Hibernate has a first level cache which is caches object for the duration
of the session.
However in your case multiple users may access the same list and this might
happen the context of different sessions. For that reason you can use
second level caches:
See here:
Exactly for that reason there are server-side caches.
Just set up a second level cache (ehcache, etc) and that should solve your
scaling issue.
If you use Spring as a backend technology it's a couple of configuration
lines to add second level cache for
Apart from caching there is the
Sorry, what is server-side caches and second level cache?
On Fri, Nov 9, 2012 at 12:50 AM, Ümit Seren uemit.se...@gmail.com wrote:
Exactly for that reason there are server-side caches.
Just set up a second level cache (ehcache, etc) and that should solve your
scaling issue.
If you use Spring
for using LIstDataProvider, if the search result contains many records and
many users use similar criteria to search simultaneously, it will use up
the memory of the server JVM easily, is this correct?
So for searching record with large result, we should use celltable with
pager and data
the title VM means server JVM.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/_FGJnN4mmzAJ.
To post to this group, send email to
A ListDataProvider does not use memory on the server JVM, it resides on the
client.
That said, an AsyncDataProvider and a pager would be far better than
reading 10,000 rows at once from the server into a ListDataProvider (which
would use a lot of memory on the client AND generate a ridiculous
