Posted: 26 May 2015 11:55 EDT Last activity: 17 Jul 2017 16:34 EDT
Progressive Paging and load times
How exactly does progressive paging work? I assume that the design principles are that the initial load should be pretty fast-- i.e., a matter of seconds, and, faster than a comparative load of the whole set of data.
On a v6.2 application, we found something a little strange -- given a dataset of ~4000 rows, in a progressive paging of showing initial 18, the HTML generated actually renders a table with the 18 rows plus 4000 empty <TR> rows -- which are to be filled in upon scrolling. That significantly slows down the browser, to the point that is takes 10s of seconds to make further HTTP requests to complete rendering the page. (Also, this problem just seemed to start recently.)
Is this how it is supposed to work in v6.2? Anyone aware if the design is changed in v6.3 / v7.1?
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
As per my understanding, Progressive paging Limits the number of rows initially loaded to render the page more quickly. Remaining items are loaded as-needed, as the user scrolls through the list. When a user drags the scrollbar and releases, all rows above that point in the grid are loaded.
Unlike traditional paging, in which users can access specific pages of data using paging controls, progressive paging enables users to access the entire data set by scrolling. Users can act on the full data set, dragging and dropping to re-order the list and sorting and filtering the entire list. For a description of a working example, see PDN article When and how to use progressive paging to load data into grids.
Progressive paging is available for all data sources, including report definition, and can be used with grids. Progressive paging is not available for tree or tree grids.