We have upgraded an application from 3.0.8 to 3.2.3 and are experiencing performance issues in an EJB which requires a secondary key and therefore doesn't use the default finder.
Basically we have a bean which provides a bi-directional map for two id's. In one direction, the beans can be cached on the PK and the operation takes under 1 millisecond, but in the opposite direction it takes between 8-20 ms and the CPU hits 100% load. Our database is PostgreSQL and I have run an explain for the required statements and I find that both lookups require about 0.1 ms(!) because both lookups are keyed. So my assumption is that the EJB/JDBC request is taking all the time. Can anyone give us some pointers as to parameters which would help to tune this operation and/or which modules we should turn on tracing for to see where the time is being used. If you need more info, I can post logfiles Thanks <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827596#3827596";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827596>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
