C
carl.williams
Guest
Had a look at this and the suggestion only helps where the first page returns less that the batch size. What is needed is for the current filtering to be stored client side and only if the filtering changes should the count function be run on the server. If whilst paging we reach a page that returns less than the page size then we no we have reached the end. If on the last page we find there are yet more records to read then we run the count again. From my tests it is often better to return the entire dataset (30,000 records) and do client side sorting/filtering, etc unless the dataset is very large. If 30,000 server filtering then the count takes 0.5 seconds on each next page. If it was 300,000 records this would make the grid very slow on page changing, approx. 5 seconds per page.
Continue reading...
Continue reading...