Specifically, the state that is passivated/stored in the DB and is preloaded.
E.g., if you preload / on startup this will take time. If you only preload
certain regions that you foresee may be needed as soon as the system starts up
(and leave the rest to load lazily), this may be quicker.
What do you mean in anonymous wrote : 2) State in your DB is large
| ? the state of the cache?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024831#4024831
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024831
It just looks like the time taken to load a lot of stuff from the cache loader.
This can be slow if:
1) Connections to your DB are slow (I'm assuming minimal overhead in
connection establishment since they're pooled)
2) State in your DB is large
In JBoss Cache 2.0.0.BETA1 (which should be
Could you enable trace level logging? Just to test where the time is being
spent? Could be in obtaining database connections - are you pooling the
connections?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024432#4024432
Reply to the post :
