Virtualization when using pagination
Virtualization when using pagination
We have a data table with a huge amount of columns (~100) and pagination enabled (~2.000 rows, 50-100 per page). The performance is "ok" since we are using "deferRender". But it could be better and we would benefit a lot from virtualization of the data table, by which only the first rows on the screen are rendered.
We noticed that the scroller has virtualization enabled, but it does not seem to work with static pagination and instead is only intended to be an "infinite" scroller. Since it's a business demand to keep our static pagination, it does not seem to be the right solution.
Is there a way to use the Scroller with "static" pagination (fixed number of rows per page) or is there another virtualization solution for DataTables?
Answers
Scroller uses DataTables' pagination to show an "infinite" scrolling table as you say. Its aim is to keep the performance benefits of paging while having the scrolling display that many like. It does not virtualise column display. It will not perform any faster than a paginated DataTable will. In fact, a scrolling table will always performance worse than a non-scrolling table due to the column width calculations involved.
So don't consider Scroller - it will not do anything to help with the large number of columns.
We don't currently have any way of vitualising column display I'm sorry to say.
If you can link to the page, I can take a look and see if there is anything we can do to suggest speed ups or where we might be able to improve our code.
Regards,
Allan