Any improvements in JBoss AS startup speed plan...| JBoss.org Content Archive (Read Only)

15. Any improvements in JBoss AS startup speed planned?

ebross Mar 26, 2011 5:35 AM (in response to henk53)

henk de boer wrote:

The first EAR is 62 MB (exploded) and the second is 10 MB (also exploded).

Okay “yours is bigger than mine” lol

With JBoss AS 6, one EAR is something like a minute and the two ears together is a minute and a half.

One minute startup per EAR? What did you say is your justification for your request for faster startup speed? One minute is not even enough time to get a cup of coffee.

JBoss startup for most users is a once a day event -- except in development and testing environments, where it is done more often. But even then, most developers would be less concerned about JBoss startup times than their program compilation times, which is done far more often.

16. Re: Any improvements in JBoss AS startup speed planned?

rmazzola Mar 26, 2011 7:10 AM (in response to ebross)

Hi All
I want report my experience...

My EAR is about 320 MB (exploded) on my laptop (i3 M330 2.13 Ghz 8 GB Ram Win 7 x64) it take about 6,5 minutes...
My ear contains EJB 2.x (entity/session), WS, war archive.
Unfortunatelly I'm a developer.. so I need to restart the server many times in a day..
I try to use the Hot deploy, but in every case when it start the server undeploy and re-deploy the full application usually
Getting a look to JBoss forum I read that one of the cause is because JBoss unpack JARs in the war\web-inf\lib and a workaround is to move
that jars in the ear\lib folder... I tested it and it is true: movimeng to ear\lib make the startup faster (not so much how jboss 4.x )
It seems that on 6.1 this issue will be fixed.
I try also to sliming asap the jboss server configuration

Think about that the same ear deployed under jboss 4.2.3 (using jdk 6) start in 3 minutes...

I agree that in a production environment usually jboss start once a day (and in the night)... but I need to reduce waiting time for developers..

I have 10 developers and they need to restart the server at least 4 or 5 time in a day... (this is the minimum times)

so 6 minutes x 5 times x 10 developers = 300 minutes --> 5 hours/day lost...

bye

p.s.: all other developer have smaller machine...

17. Any improvements in JBoss AS startup speed planned?

henk53 Mar 27, 2011 8:18 AM (in response to ebross)

One minute startup per EAR? What did you say is your justification for your request for faster startup speed?

Well, it was faster in JBoss AS 5 and JBoss AS 6 was supposed to be faster not slower, wasn't it?

I do agree that this minute is not the end of the world, but I'm a developer who somewhat specialized in high performance computing in the past, so it's a natural instinct of me to ask "why isn't this stuff going faster". When I look at my resource usage during startup, they are only very moderately being used. So theoretically, this could go way faster.

And indeed, a minute is not enough to get a cup of coffee, especially when in my case I make it using an old-fashioned machine and have to adjust the pressure, steam milk, carefully clean afterwards, etc

18. Any improvements in JBoss AS startup speed planned?

genman Mar 27, 2011 9:54 AM (in response to henk53)

I wonder if it has to do with the annotation scanning process?

You can disable much of the scanning through configuration.

19. Re: Any improvements in JBoss AS startup speed planned?

henk53 Mar 27, 2011 11:27 AM (in response to genman)

Elias Ross wrote:

I wonder if it has to do with the annotation scanning process?

You can disable much of the scanning through configuration.

I know, however I do value having those annotations a lot. If it's indeed the (extra) annotation scanning then it's something I don't mind to pay the extra wait for.

On the other hand, I was already using JPA and EJB on AS 5 and those also necessitate scanning for annotations. I don't have a beans.xml file at the moment and JSF currently operates in 1.2 mode (via a 1.2 declaration in faces-config, because of major problems with RF4), so how much extra annotation scanning would there be between Java EE 5 and 6?

One suspicious delay is right in the beginning:

17:19:34,039 INFO  [JSFImplManagementDeployer] Initialized 3 JSF configurations: [Mojarra-1.2, MyFaces-2.0, Mojarra-2.0]
17:19:39,572 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
17:19:56,940 INFO  [PersistenceUnitValueMetaData] iDependOn persistence.unit:unitName=jboss-ejb3-timerservice-mk2.jar#timerdb
17:20:01,639 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@690392502{vfs:///Users/myuser/jboss-6.0.0.Final/server/default/deploy/my.ear/my_ejb.jar/}

There's an initial 17 seconds delay when JBoss AS is most likely inspecting my EARs (if I have an error in one of them, this is typically reported a few seconds after the "AIO" log line.

20. Any improvements in JBoss AS startup speed planned?

genman Mar 28, 2011 2:43 PM (in response to henk53)

You can enable/disable annotation scanning selectively, by package and by jar. I would probably try to deploy with it entirely off (and break your app), and see if the times improve. The documention is pretty weak: http://java.dzone.com/articles/jboss-microcontainer-scanning

I did do some profiling recently and the deployment time went way, way down. (This was when I disabled unpacking of .war files.) I got a test app (18MB) deployed in about 10 seconds down from over a minute.

You can get a lot of milage out of a profiler: If you attach when JBoss is deploying, it's fairly easy to spot the issues internally. Providing a patch is another story.

I would suggest to Roberto: Use a ram disk for JBoss temp. Profile your deployment. Restructuring often-changed parts of your deployment into a separate deployment units and access your EJB over JNDI.

21. Any improvements in JBoss AS startup speed planned?

jaikiran Mar 29, 2011 4:21 AM (in response to genman)

Elias Ross wrote:

You can get a lot of milage out of a profiler: If you attach when JBoss is deploying, it's fairly easy to spot the issues internally. Providing a patch is another story.

Just a note - In general, if anyone has any such details and if it's worth mentioning, then please do provide those details either in these forums. Doesn't matter if you don't have a patch. Someone else might find some time to provide a patch and fix it.