Comments on: Survey Results: The Java EE Container Redeploy & Restart Report – measuring Turnaround Time

By: melbeltagy

melbeltagy — Thu, 24 Sep 2009 13:42:34 +0000

We’re using Websphere and we don’t redeploy at all. We run in debug mode, using RAD from within our workspace.
Whatever changes happens are deployed automatically by WAS for Java classes and JSPs. Even for EJBs.
We only have to restart the server if we change an EJB’s method’s signature, which is rarely.
Restart time takes about a minute or two, max. Is that an issue? Of course not.

By: Denis Robert

Denis Robert — Thu, 24 Sep 2009 10:48:13 +0000

@searchfull: Ever work with Websphere? 10 seconds doesn’t even get you past the first steps in deployment. Deploying on websphere has sometimes taken me up to half an hour, for something I would consider a smallish app. Even with perfect optimization, you’d be lucky to get your deploy time under 5 minutes.

Not to mention the number of times a clean restart is required, even though IBM would like you to believe it never is…

By: George

George — Thu, 24 Sep 2009 10:43:45 +0000

So those who choose Weblogic and Websphere not only choose to pay Oracle/IBM instead of get free software, they choose to waste developers’ time as well. The good old fashioned “choosing IBM won’t get you fired” turns out to be irresponsible incompetent choice. These companies deserve to suffer…..

By: searchfull

searchfull — Wed, 23 Sep 2009 13:58:22 +0000

If your compile-deploy cycle lasts more than 10 seconds, you’re doing it very wrong. Make your war smaller and more modular, use a IDE plugin for deployment, use lazy initializations, and separately-deployed resource pools.

By: Jevgeni Kabanov

Jevgeni Kabanov — Wed, 23 Sep 2009 08:36:25 +0000

@Lars

Not sure if there’s a big difference in the lineup. Plus why would frequency of redeployment depend on container?

By: Toomas Römer

Toomas Römer — Wed, 23 Sep 2009 07:57:51 +0000

@Jan

Thanks for the correction and the speedy container!

By: Lars Clausen

Lars Clausen — Wed, 23 Sep 2009 07:55:13 +0000

The comparison of containers based on how much time developers spend on redeploying them is rather misleading — that assumes that the frequency of redeployment is independent of container. Here’s a breakdown of average deployment time for the deployment systems. Caveats about project size still applies, of course – would have been nice to know the number of classes/number of beans/other size measurement.

Server Redeploy average
Jetty 1,153
Apache Tomcat 1,669
Caucho Resin 1,735
GlassFish 1,900
JBoss 2,705
Oracle OC4J 2,924
Oracle Weblogic 3,606
IBM WebSphere 3,845

By: Jan Bartel

Jan Bartel — Wed, 23 Sep 2009 00:41:47 +0000

As a Jetty committer it’s nice to see our efforts to keep jetty small, fast and flexible are paying off!

One thing I have to correct though is that Jetty does indeed support redeployment. In fact we support it 4 ways: in the standalone container via our ContextDeployer, in the maven jetty plugin, via jmx using the WebAppContext mbean and programatically when running jetty embedded.

cheers
Jan

By: Toomas Römer

Toomas Römer — Tue, 22 Sep 2009 17:22:23 +0000

@Henry What are the redeploy times for Android emulator?

By: Henry

Henry — Tue, 22 Sep 2009 16:32:52 +0000

I wish you guys could also solve my “deploys” in Android development….then my (programming) life would be set.