incendio Well-Known Member Licensed User Longtime User Jan 4, 2019 #1 Hi guys, Just tried latest xui view from this post : https://b4x.com/android/forum/threads/b4x-xui-views-cross-platform-views-and-dialogs.100836/ Running on GenyMotion with Android 4.2.2, just run and do nothing, and noticed high CPU utilization. Don't know which component that caused this.
Hi guys, Just tried latest xui view from this post : https://b4x.com/android/forum/threads/b4x-xui-views-cross-platform-views-and-dialogs.100836/ Running on GenyMotion with Android 4.2.2, just run and do nothing, and noticed high CPU utilization. Don't know which component that caused this.
Erel B4X founder Staff member Licensed User Longtime User Jan 4, 2019 #2 incendio said: just run and do nothing Click to expand... It is not really doing nothing. The animated views are configured to update every 16 ms. Remove the animated progress bar and the activity indicators and check it. Upvote 0
incendio said: just run and do nothing Click to expand... It is not really doing nothing. The animated views are configured to update every 16 ms. Remove the animated progress bar and the activity indicators and check it.
incendio Well-Known Member Licensed User Longtime User Jan 4, 2019 #3 Erel said: It is not really doing nothing. The animated views are configured to update every 16 ms. Click to expand... Nothing = no user activity. Removed animated progress bar,indicators and scrolling label return CPU utilization to normal again. This 3 components really hog CPU performance, should be use only in short time period. Upvote 0
Erel said: It is not really doing nothing. The animated views are configured to update every 16 ms. Click to expand... Nothing = no user activity. Removed animated progress bar,indicators and scrolling label return CPU utilization to normal again. This 3 components really hog CPU performance, should be use only in short time period.
Erel B4X founder Staff member Licensed User Longtime User Jan 6, 2019 #4 2 points: 1. Never test performance on a VM. It is not relevant. 2. The example shows three different animated "busy indicators" at once. This is not a real use case. Upvote 0
2 points: 1. Never test performance on a VM. It is not relevant. 2. The example shows three different animated "busy indicators" at once. This is not a real use case.
incendio Well-Known Member Licensed User Longtime User Jan 6, 2019 #5 1. I can test it on real device, but i suspect, it will have similar effect on cpu. 2. I didn't say it was bad, but just reminder that developer that use these component should be aware of its impact on cpu utilization. Upvote 0
1. I can test it on real device, but i suspect, it will have similar effect on cpu. 2. I didn't say it was bad, but just reminder that developer that use these component should be aware of its impact on cpu utilization.
