jQuery UI Widgets › Forums › TreeGrid › Tree Grid Expand and Collapse Row is slow
Tagged: treegrid widget
This topic contains 23 replies, has 5 voices, and was last updated by dpibt 8 years, 10 months ago.
-
Author
-
Hi Peter
We have used virtual mode for loading child elements still in IE the loading time is very slow .is there any solution we can build with out paging and if we need to use paging what will be the maximum number of records we can show in single page .I tries paging with 50 records but still it is very slow .Let me know your thoughts on it
Thanks and Regards
Anand.RHi Anand.R,
If you used this approach: http://www.jqwidgets.com/jquery-widgets-demo/demos/jqxtreegrid/javascript-tree-grid-virtual-mode.htm?arctic, I don’t think it would be slow in any browser. Paging is required if you want to display many records due to the fact that the TreeGrid creates HTML Element for each data value and when paging is enabled, it will create HTML Elements only for the data values displayed on the Page. It is up to you what value for pageSize you will use in your TreeGrid. It’s a personal preference.
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comHi Peter
Thanks for the response ..My problem is that am having around 50 columns in the grid.So when ever it renders it hangs on ie and for expand and collapse also it is taking some time
Thanks in advance
Anand.RHi Anand.R,
I understand that you don’t like how our control behaves in your scenario. Sorry, but there’s nothing else what I can do for you. If you wish use it with Paging enabled and with default or small page sizes to reduce the number of visible html elements, but if you wish do not.
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comHello,
We are having the same problem, the performance is horryble, taking up to one minute to load a grid with 1000s or rows.
It seems that the problem is quite simple, there are forced reflows happening and this can be prevented if the things are done correctly, we’ve been able to analyse this through JS profiling.
We need that the paintings and property changes are done correctly because paging or virtual mode is no a sollution
Hi dpibt,
Here’s a treeGrid with 10 000 rows taking less than second to load: http://www.jqwidgets.com/jquery-widgets-demo/demos/jqxtreegrid/javascript-tree-grid-virtual-mode.htm?light. Use the same approach to have a good performance.
If you want to load big amount of data, you have and should use Paging, not to load All your data in the DOM which always will be slow with any tool.
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comOur customer needs to have all nodes open and visible (without virtualmode and without paging)
We’ve analized the js execution and it seems that “Forced reflows” are ocuring, this means that a CSS property is changed with JS and accessed with JS before it’s drawn, this means that it needs to draw the change internally to give an answer to the accessing
If the element is completely defined before being drawn this “Forced reflow” doesn’t happen.
Is this planned for future releases?
Hi dpibt,
We do not think that any changes in jqxTreeGrid should be made in future versions regarding this. By design the widget works with many items only in Paged mode. We have no plans to implement virtual scrolling in the TreeGrid in order to support multiple records without paging. CSS property is not changed with javascript during re-rendering, too. The entire view is built as HTML String and then set with one only javascript innerHTML call.
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comWe’ve checkend and verifyed that css properties are setted and getted during the drawing and this causes forced (or synchronous) reflows.
Thank you
-
AuthorPosts
You must be logged in to reply to this topic.