Extremely slow grid performance when editing in IE and Edge

3 posts, 0 answers
  1. Daniel
    Daniel avatar
    11 posts
    Member since:
    Apr 2016

    Posted 06 Apr 2017 Link to this post

    We have serious performance issues in IE (Edge is also quite slow) when editing fields in a grid. Our grids have  in general 10+ columns and 50+ rows.

    The page consists of  2 tabs, where the first tab contains a grid.

    When trying to edit a numeric text field, the operation is very slow. Even the field selection lasts around 3-4 seconds. I am aware that there are issues regarding performance in IE but is there anything that we can change in our implementation to improve the performance but keep the functionality? 
    Our application is unusable in Internet Explorer with the current setup.

    Grids have all operations enabled: 

    • filtering(row) - server side
    • sorting(multiple) - server side
    • grouping - server side
    • selection (multiple row)
    • paging - server side
    • editing
    • export

    Grids have detail rows which consist of 3 or more tabs. And each tab has either a grid (smaller than the main grid) or numeric text fields (10+).

    I prepared a few grid examples to be able to debug the slow performance:
    There is a JSP Kendo grid version and JS grid version with attached diagnostic sessions screenshots. Based on the IE diagnostic session on "mousedown" there are repeated offsetwidth calculations triggered which are propagated to every element in the main grid and this is repeated in our example's case 10 times. Is there a way to avoid this triggered calculations?

    Our Kendo Library version is 2016.3.914 (but I tested it with the latest 2017.1.223 with the same results)


    Thanks in advance for any ideas!

  2. Viktor Tachev
    Viktor Tachev avatar
    2468 posts

    Posted 10 Apr 2017 Link to this post

    Hi Daniel,

    Please refer to the answer in the support ticket you have submitted. In case you have additional queries I suggest we continue the conversation there. 

    If you would like you can share the resolution in the public thread. That can help someone with observing similar behavior.

    Viktor Tachev
    Telerik by Progress
    Try our brand new, jQuery-free Angular 2 components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
  3. Daniel
    Daniel avatar
    11 posts
    Member since:
    Apr 2016

    Posted 12 Apr 2017 Link to this post

    Based on the conversation in the support thread, the conclusion is that in order to improve our grid's performance we have to reduce the pageSize. And we also noticed a bit of an improvement when we disabled 'grouping' and 'navigatable' features in the grid. 

Back to Top