-
1. Re: CMP, Cache, and Performance Degradation
benw Jul 22, 2002 2:56 PM (in response to asharzaman)I am having the same problem. I have an entity that contains 976 records. With commit option A and read-ahead set to either on-load or on-find, the findAll() call basically gets all the data from the database the first time around (which is fine). However, when I tried to access the data the 2nd time, it took over 40 secs to return the data from the cache. I tested this using JBoss 3.0.0 final and JBoss 3.0.1 rc1. JBoss 3.0.0 final was even taking longer, often over 90 seconds for the data to come back from the cache.
Any insights on this will be greatly appreciated,
Ben -
2. Re: CMP, Cache, and Performance Degradation
asharzaman Jul 22, 2002 6:07 PM (in response to asharzaman) -
3. Re: CMP, Cache, and Performance Degradation
dsundstrom Jul 24, 2002 1:27 AM (in response to asharzaman)Are you sure this is in the entity cache? If so, I suggest you bring this up on the JBoss-dev list.
-
4. Re: CMP, Cache, and Performance Degradation
asharzaman Jul 24, 2002 6:08 PM (in response to asharzaman)may be i don't know how to set the entity-cache. I was thinking that list-cache-max is how it was set. can someone please tell me where and how to setup entity cache.
thanks -
5. Re: CMP, Cache, and Performance Degradation
dsundstrom Jul 28, 2002 1:54 AM (in response to asharzaman)list-cache-max is a query results cache. The bean cache is controlled by the jboss.xml file. I don't know the setting but look for the cache section.