So Grid virtual scrolling is a great concept and allows us to show large amounts of data with good performance. The problem we have is that it couples two unrelated performance bottlenecks into a single pageSize variable on DataSource:
1. Backend/Remote fetch performance and processing.
2. Client side HTML rendering performance.
Generally speaking we can fetch a large number of items from the Backend without hitting any performance bottlenecks. This makes for the most efficient use of bandwidth (smaller HTML request overhead) and a better user experience (don't keep hitting the load bar). The problem is that if we tune a larger value for pageSize to make (1) work better, then suddenly we start hitting Client side rendering bottlenecks in (2).
In an ideal world the pageSize used by the Grid for display virtualization would be an independent value that could be tuned differently to the pageSize of the DataSource. Is there a way to achieve this in the current library? I was thinking perhaps I could somehow wrap a remote DataSource with pageSize A in a local DataSource with pageSize B, and then set the local DataSource on the grid.