On Sat, May 12, 2012 at 12:39 PM, Emmanuel Bernard <emman...@hibernate.org> wrote: > 10-20 seconds? For how many classes in your app ?!
Probably quite a lot because it scans the whole classpath but nothing weird as our applications are "just" Spring-*/Hibernate-*/Wicket applications. The scan in Tomcat isn't really optimized in terms of IO (a lot of random IO throughout all the jars and it would probably be better with sequential access). I wanted to give a shot at optimizing that but I haven't found the time yet. The Servlet 3 + Java configuration cost was really unacceptable (and buggy) before Tomcat 7.0.26 (+ 30-40 seconds on each startup) where the scan for interfaces and annotations configuring the servlet environment was entirely rewritten. > Use a real app server man, we worked hard to reduce this time in JBoss AS :) Yeah, well, last time I checked, it wasn't so amazing but it was a long time ago. Without using the new Servlet 3 java configuration, Tomcat + our applications usually start in 10-15 seconds in our dev environment (and even less on our servers) so it's quite good. -- Guillaume _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
