Reference Information. I am working on converting multiple pages in our applications to use AngularJS as an attempt to overhaul the architecture. So far, Angular has turned out to be friendly to me, and its learning curve is quite sharp, but everything is in order.
On one of our main pages, we have slickgrid, and I decided to use ng-grid instead of slickgrid to save myself from a headache in my first pass. Due to the nature of our application, the same data will be filtered / not filtered many times during the life cycle of the page. The entire data set will always remain the same, and so far there are only 20-40 data points.
The functionality in which it works overwrites data for gridOptins.data . Nevertheless, serious performance is observed, as the memory increased from ~ 20 MB to ~ 64 MB only during several filtering cycles. And it becomes slow (> 40 ms) for the grid to complete reprocessing. The timeline profiler shows that a huge amount of DOM is created each time the grid data changes.
I made sure that it is not advisable to often remove / insert data points from ng-grid, and I am looking for some workaround for this problem. One of them simply hides the data point, but I have not yet seen examples illustrating this.
Other suggestions are also welcome.
edit: Here plunkr:
http://plnkr.co/edit/dgA2HW
Try to click the filter often and watch how shared memory is created.
source share