I traced through the code and found that the majority of the time for processing of one POJO object (14 seconds out of 17 seconds) was spend in JDBCCacheLoader.put(List modifications)
The insert of serialized object into DB didn't take any more than 300 miliseconds. The POJO object has about a 100 fields, primitives mostly, distributed between 3 different interfaces, one interface extending another, all the way to the POJO object that implements the aggregate interface. This delay however seems to be only endemic of the JDBCCacheLoader. The FileCacheLoader does not display this kind of behaviour. I can put togehter a test case and upload to Jira ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914099#3914099 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914099 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
