Hi,
I have a web app based on Kendo UI, and it works sufficiently well on desktop and on the iPad.
Now I want it to be used by Android tablet users, but tests show that performance will be a problem.
It manifests even on Kendo UI demos itself, with a grid and nothing else: http://demos.telerik.com/kendo-ui/grid/index.
On a tablet with 4x1.6 Ghz CPU it takes 5 seconds for the data to show in a grid after page refresh, which is already too much for such a simple page.
On a tablet with 2x1.0 Ghz CPU it takes 10-11 seconds even!
That's when all the resources used should be cached already.
Are there any guidelines to improve the performance on Android?
I do need to run the app on lower end devices, and 10+ seconds to initialize stuff is just unbearable.
I have a web app based on Kendo UI, and it works sufficiently well on desktop and on the iPad.
Now I want it to be used by Android tablet users, but tests show that performance will be a problem.
It manifests even on Kendo UI demos itself, with a grid and nothing else: http://demos.telerik.com/kendo-ui/grid/index.
On a tablet with 4x1.6 Ghz CPU it takes 5 seconds for the data to show in a grid after page refresh, which is already too much for such a simple page.
On a tablet with 2x1.0 Ghz CPU it takes 10-11 seconds even!
That's when all the resources used should be cached already.
Are there any guidelines to improve the performance on Android?
I do need to run the app on lower end devices, and 10+ seconds to initialize stuff is just unbearable.
6 Answers, 1 is accepted
0
Hi,
I tested the demo in question on a Nexus 7 tablet (2+ years old). A full page reload took less than 5 seconds.
In general, the older Android devices/OS versions are severely underpowered and are not capable of running complex UI. Major part of the slow performance is the network itself, in fact.
To obtain further insight into what slows your case down, you can debug the device remotely and use the network/timeline tabs to see what takes the most time.
Regards,
Petyo
Telerik
I tested the demo in question on a Nexus 7 tablet (2+ years old). A full page reload took less than 5 seconds.
In general, the older Android devices/OS versions are severely underpowered and are not capable of running complex UI. Major part of the slow performance is the network itself, in fact.
To obtain further insight into what slows your case down, you can debug the device remotely and use the network/timeline tabs to see what takes the most time.
Regards,
Petyo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Hans
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2014, 02:27 PM
Thank you for your reply.
In fact, I've tried that on the grid demo page (http://demos.telerik.com/kendo-ui/grid/index), using Chrome browser, and most time is consumed by "scripting"; with big chunks of it being unexpected GC events and evaluating scripts - check the files attached .
The device I have to run it on is not a high end one for sure, it's based on Rockchip RK3066 with 2 ARM Cortex-A9 cores at 1 Ghz; but as a comparison, it's Antutu benchmark result is 11578 - not *that* less than typical 12-13k for Nexus 7.
Is there anything we can do to make it faster? Because currently the only option we have is to abandon Kendo and use some more lightweight alternatives for our grids and treeviews :(
In fact, I've tried that on the grid demo page (http://demos.telerik.com/kendo-ui/grid/index), using Chrome browser, and most time is consumed by "scripting"; with big chunks of it being unexpected GC events and evaluating scripts - check the files attached .
The device I have to run it on is not a high end one for sure, it's based on Rockchip RK3066 with 2 ARM Cortex-A9 cores at 1 Ghz; but as a comparison, it's Antutu benchmark result is 11578 - not *that* less than typical 12-13k for Nexus 7.
Is there anything we can do to make it faster? Because currently the only option we have is to abandon Kendo and use some more lightweight alternatives for our grids and treeviews :(
0
Hans
Top achievements
Rank 1
Rank 1
answered on 20 Nov 2014, 02:32 PM
Here go the images
0
Hi,
One of the things you can do is to reduce the script evaluation times by building a custom script. However, 4 seconds parsing seems really slow, which means that most likely other parts will be slow too. If such devices are to be supported, you may treat them like a mobile ones, and use the Kendo UI mobile application and the rest of the mobile widgets for that purpose.
Regards,
Petyo
Telerik
One of the things you can do is to reduce the script evaluation times by building a custom script. However, 4 seconds parsing seems really slow, which means that most likely other parts will be slow too. If such devices are to be supported, you may treat them like a mobile ones, and use the Kendo UI mobile application and the rest of the mobile widgets for that purpose.
Regards,
Petyo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Hans
Top achievements
Rank 1
Rank 1
answered on 24 Nov 2014, 01:58 PM
Hi,
Thanks for a hint,
Indeed I already tried custom Kendo script – it improves things, but it's not enough to make performance decent on the target device.
Speaking about mobile widgets, they don't include datagrid or treeview, do they?
Thanks for a hint,
Indeed I already tried custom Kendo script – it improves things, but it's not enough to make performance decent on the target device.
Speaking about mobile widgets, they don't include datagrid or treeview, do they?
0
Hello Hans,
Yes, the mobile widgets do not include grid/treeview. You can browse our demos for more details on what's included in the mobile category.
Regards,
Petyo
Telerik
Yes, the mobile widgets do not include grid/treeview. You can browse our demos for more details on what's included in the mobile category.
Regards,
Petyo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!