ok, now i had a look at the BDbje code and noticed that it takes about 60
percent of the total memory, which is 60 percent of the 1024 i allocated in
Xmx. so it caches all the objects already present in jbosscache and the copy of
all this i s also there in the persistent storage.
now je is sup
One more thing i noticed. i turned off the caccheloader completely, i.e no
bdbjeloader. so when the evict is called it is evicted from in-memory. In this
case once my operation is complete and eviction happns the jvm comes back to
the state before i started. so here are my results :
1. withcach
Yes u are right, i call remove instead of evict when maxage is reached.
i am using the Jboss Cache 1.4 , i think jalapeno...so that wud be a remove
call on TreeCache. This wud be the (2) u were talking abt ?
my cache config file as in u mean the jboss-service.xml ?
i am using jboss cache to cache string objects with a key. these are basically
xml string but stored as plain java strings. I have written a customLRUPolicy
wherein at the end of day when maxage is reached (86400 seconds) the object is
removed from cache rather than evict. otherwise no differenc
