[jboss-dev] AS trunk boot time back to poor?
David M. Lloyd
david.lloyd at redhat.com
Thu Jan 21 11:39:29 EST 2010
On 01/21/2010 09:55 AM, Brian Stansberry wrote:
> 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.
If you also add -Djboss.server.log.threshold=INFO as well (which makes
little difference in total output, but filters log messages much sooner),
you might gain a couple more seconds (mine went from 44 to 42).
> Question: should INFO be the default for boot.log?
>
> My opinion is yes.
Then perhaps the global threshold should also be INFO.
> 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.
This is a side-effect of using a MC schema deployer. If this is
undesirable it can be addressed, theoretically anyway.
- DML
More information about the jboss-development
mailing list