Paging Slow After Sorting

[Michael Eaton]

Loading all of the data initially (using an observer/async). Grid pages quickly after we load 60k records into it. After applying a sort the paging becomes extremely slow (takes several seconds/page). Has anybody else ran into this situation/how do you resolve it?

Thanks,

Mike

[Thavasianand Sankaranarayanan]

Hi Michael, 

Greeting from Syncfusion support. 

We have validated the provided information. By default while binding large amount of data then it take considerable time perform actions. We suggest you to use paging feature to load the data on demand basis. Please refer the below help documentation and sample for more information. 

In the below sample, we have load the data based on the skip and take value you can also use this way to achieve your requirement. 

Sample : https://stackblitz.com/edit/angular-ntgj93-j9ubcg?file=async-pipe.html 

Help documentation : https://ej2.syncfusion.com/angular/documentation/grid/observables/#handling-grid-actions 

https://ej2.syncfusion.com/angular/documentation/grid/paging/ 

Please get back to us if you need further assistance on this. 

Regards, 

Thavasianand S. 

[Michael Eaton]

Thanks for the reply Thavasianand.

What is confusing is it seems to be fast when not sorted but only slows down after being sorted. Can you explain why it only slows down after the sort?

Thanks,

Mike

[Thavasianand Sankaranarayanan]

Hi Michael, 

By default, while perform grid actions like sorting, filtering etc.., then we have send request and get result from server and bind it to the Grid so it take time(based on your services) to get data from server and render the cells(60,000*5(columns) = 300000 cells) in grid(with new data) so that we suggest you to use on-demand (paging) loading concept for large data. 

Regards, 

Thavasianand S. 

[Michael Eaton]

Thavasianand,

I think you are misunderstanding me. We preload all of the data to the client so it doesn't have to get the data every time an action is preformed. We also have it set to only render 10 rows at a time (not 60000), which is our default page size. The issue isn't with the slowness of our data loading from the server + initial rendering. That works plenty fast for us. Paging is fast, filtering is fast, everything is fast initially. The problem doesn't start until after I perform a sort on data this is already loaded. The data sorts plenty fast but it slows paging way down when I have anything but the default sort. I'm sure your recommendation would work but I'm trying to make sense of the existing behavior.

Thanks,

Mike

[Seeni Sakthi Kumar Seeni Raj]

Hi Michael, 

By default, Grid will need to maintain the previously performed actions (like sorting, filtering, etc..) after performed the paging. If you were performed sorting before the paging, then (while paging) the Grid will sort its whole datasource again (based on the maintained sort query) and take the records from the newly sorted datasource for the new page (to maintain the sorting). So, this time delay will occur while occur. 

Regards,  

Seeni Sakthi Kumar S. 

[Michael Eaton]

Seeni,

Thanks for the explanation, that is what we suspected was occurring.

Mike

[Sarasilmiya Shahul Hameed]

Hi Michael, 

  

Thanks for your response.Please get back to us if you need further assistance. 

  

Regards, 

Sara