GC was suggested by Brian. :-)

Since the major cost of POJO cache (TreeCacheAop) is in putObject (it has to 
map the object recursively into primitive fields), I'd say benchmark putObject 
with different POJO every time is probably not a good idea. It is probably not 
a good use case anyway.

Ideal case is putObject mostly while do POJO get/set methods.

If you are interested to cook up a more complete test case, let me know.

-Ben

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910160#3910160

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910160


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to