Re: Grid Pagination and Performance

On Thu, 14 Nov 2013 00:33:04 -0200, Thai Tran wrote: Thank all for your answers. What I am really confused is the official document does not say anything about the performance, while I can see clearly that in my persisted list, there is 10k objects transferred back and forth between client and

Re: Grid Pagination and Performance

On Wed, 13 Nov 2013 20:29:51 -0200, Lance Java wrote: The grid needs the rowcount to know how many pages there are in total (eg page 1 of N). HibernateGridDataSource and JpaGridDataSource execute 2 types of queries. 1 to get the rowcount and another to get a single page at a time. In my

Re: Grid Pagination and Performance

The Grid should only ever send a single page of data at a time. Let's get things clear... Are you using @Persist or java.util.List with your large dataset? To maintain scalability you should never coerce GridDataSource to List. Perhaps it's just your choice of language (persist & list) that was

Re: Grid Pagination and Performance

Thank all for your answers. What I am really confused is the official document does not say anything about the performance, while I can see clearly that in my persisted list, there is 10k objects transferred back and forth between client and server even the rowsPerPage is set to 20. I think there s

Re: Grid Pagination and Performance

The grid needs the rowcount to know how many pages there are in total (eg page 1 of N). HibernateGridDataSource and JpaGridDataSource execute 2 types of queries. 1 to get the rowcount and another to get a single page at a time. In my opinion this is a scalable approach.

Re: Grid Pagination and Performance

@Thai, you can implement your own GridSource for better performance. Check this threadfor help. *-* *Muhammad Gelbana* http://www.linke

Re: Grid Pagination and Performance

Hi, You are correct that the current provided implementations of the GridDataSource (HibernateGridDataSource and JpaGridDataSource) will query for the total number of rows in the database and therefor can kill performance on the client side as well as on the DB side. Particulary if sorting and