Large dataset makes the grid really slow
Anything I can do to optimize for the large dataset ?
Thank you for your help
Any thought about the slowdown ?
Maybe latest 1.0 version fixed this leeks ?
I give users the tools to filter their searches and figure if they max out the number of rows then that they can learn to filter better.
I don't think you will find another component that does what this does.
The memory leaks is a different issue. Every effort had been taken to eliminate possibility of memory leaks in ActiveWidgets library. So far I am not aware of any memory leaks in the current version. If anyone sees memory leaks related to ActiveWidgets code - please let me know.
It takes maybe a second on my system right now to sort, which is fine with me (considering I have more things open than NASA right now)
Those timings are approximate. ;-)
Thanks in Advance.
theDiv.innerHTML = awObj;
Alex, This really is the best Web client grid I've seen in my years and I'd love to be able to purchase it for use in my application if I can get it to meet my needs. Do you have any suggestions for how to use your AW Grid with data requirements of such a large size?
Any help would be greatly appreciated...
Would be great if what you say is true.
I would say that the only real solution for large datasets is paging - but this trick can significantly improve 'perception of speed'.
If you do some testing you are actually going to find that the total time to load the page goes down using my trick. We brought a 20 second total load time down to about 7 seconds. It surprised us, but we did many tests and they all bore similar results.
I kinda dissagree with paging as the ultimate solution to the strategy. The two best ways to truly solve the problem are:
1) Virtual Mode: Don't render rows until they come into view. Look at the stats, it take 95% of the time to render the rows, and 5% to load and sort the data. Domapi (www.domapi.com) v4 has a listgrid that is very mature and supports this functionality. A quick test of Domapi's listgrid with Virtual Mode On vs. Off shows a DRAMATIC improvement speedwise from only rendering rows in view.
2) Seemless Paging: Use AJAX calls for data everytime the grid is loaded,scrolled or sorted. ive seen random implementations of this in custom grid components online, and its surprisingly effective, and enables the grid to work with infinite size data sets .
#2 Is complex to implement, but virtual mode is very implementable. Alex if you want some ideas how to do it, i recommend taking a look at the domapi source.
I get a 2000 rows 20 cols, render in les than 1 sec. suing simple DOM techniques.
This topic is archived.
Back to support forum
Version 2Looking for AW 2.6 ?
The old site is here.