Hey all
As Marc outlined there was a performance problem with EntityBeans. The
JAWS handling took way too much time resulting in bad performance.
I just got my registered version of OptimizeIt today (VERY nice tool
BTW!), and used it to check EntityBean usage. Found the problem right
away: the old JDBC pool (that I wrote) was used, and it re-created a
dynamic proxy on each close() (performed very often). This was very very
bad, so I changed it so the code did not have to do this.
Performance for EntityBeans is now as it should be, i.e. around 2-3 ms
per call. :-)
(BTW, we should change the default configuration to use the Minerva
pools which seem to be more capable and complete. Is there any reason we
don't do this?)
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
