Next up, get rid of the 20.6MB of boot.log that's created when this app
is deployed. (Even w/o it, our boot.log was ridiculously big, IIRC > 7MB.)
Adding -Djboss.boot.server.log.level=INFO (see [1]) cuts another 4 secs,
down to 40.2.
Question: should INFO be the default for boot.log?
My opinion is yes.
Note that boot.log now includes almost the entire boot sequence, with
server.log kicking in only at the very end, so file sizes are not
directly comparable to previous releases.
[1]
http://community.jboss.org/docs/DOC-10235
On 01/21/2010 07:47 AM, Jaikiran Pai wrote:
After today's "svn up" of my workspace, i see that the
"default"
instance boot in around 48 to 50 seconds:
19:10:18,431 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer]
JBossAS [6.0.0.SNAPSHOT (build: SVNTag=JBoss_6.0.0-SNAPSHOT
date=r99718)] Started in 48s:36ms
The only noticeable change that i have seen is related to admin-console
being included in AS trunk. So i removed the admin-console.war from the
deploy folder and the server boots in 23 to 25 seconds. Adding it back
to deploy folder takes the boot time to 48 to 50 seconds consistently. I
haven't yet looked at where the time is being spent for deploying this
single app. But clearly it increases the boot time by almost 25 seconds.
Anyone else seeing this drastic change in boot time?
regards,
-Jaikiran
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat