I'm using the Kendo UI Web controls with ASP.NET MVC 3 on .NET Framework 4.0. We've been developing a new application that uses Kendo controls extensively. Grids with custom toolbars, command buttons, ~20 columns, and editor templates are used heavily.
I've been running the application side by side on IE 8 and Chrome. The performance on Chrome is significantly better (~5X better). It's most notable with the Kendo Grids. On IE8 there seems be a notable lag between loading the data and then displaying the data on grids. Same for going in and out of edit mode. It's not taking CPU processing time during this lag. It takes a few seconds to refresh the grid once the data is loaded. In Chrome it's pretty must instantaneous.
Unfortunately IE 8/9 are our official browsers. Any tips to improve performance? Our users won't accept the performance as it currently sits.
1 Answer, 1 is accepted
0
Hi Jeff,
IE's rendering and Javascript engines are multiple times slower, compared to those of Chrome, so achieving the same level of performance and responsiveness in heavy resource-intensive web pages is practically impossible, no matter how much we try to optimize the source implementation:
http://sixrevisions.com/infographs/browser-performance/
In case the application is pushing IE to its limits, you can try optimizing the performance by reducing the amount of rendered / generated HTML markup and reduce the amount of initialized client widgets, components, etc. For example:
+ load more parts of the page and initialize more widgets on demand only when needed
+ use fewer rows for the Grid by changing the paging settings.
+ try different Grid edit modes and compare which is faster in your case
Regards,
Dimo
the Telerik team
IE's rendering and Javascript engines are multiple times slower, compared to those of Chrome, so achieving the same level of performance and responsiveness in heavy resource-intensive web pages is practically impossible, no matter how much we try to optimize the source implementation:
http://sixrevisions.com/infographs/browser-performance/
In case the application is pushing IE to its limits, you can try optimizing the performance by reducing the amount of rendered / generated HTML markup and reduce the amount of initialized client widgets, components, etc. For example:
+ load more parts of the page and initialize more widgets on demand only when needed
+ use fewer rows for the Grid by changing the paging settings.
+ try different Grid edit modes and compare which is faster in your case
Regards,
Dimo
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!