Re: Performance degradation with Derby Embedded under Tomcat vs Jetty
I've tried to figure out what the differences are between these two environments without luck. Perhaps the amount of memory available to Derby is dramatically different in the one case than in the other, and Derby is working very hard to accomplish its tasks with insufficient memory? bryan
Re: Performance degradation with Derby Embedded under Tomcat vs Jetty
I found another crucial clue: if I use ClientDriver instead of EmbeddedDriver and connect to the Derby database running under Jetty, I get identical performance with Tomcat and Jetty. This is very strong indication that there is something about the combination of EmbeddedDriver and Tomcat that is gumming up the works. -- Øyvind Harboe - Can Zylin Consulting help on your project? http://www.zylin.com/
