JBoss 4.3 start up time information

[chiewming]

Hi All,

My customer bought a Sun Fire T5120 and he is complaining the JBoss startup time is very slow comparing to their 4 core Xeon.

Setup as below:
====================
Platform : T5120
Core : 4 (8 Threads each core)
RAM : 8GB
JBOSS : 4.3
Java : 1.5.0.15
Java : -Dprogram.name=run.sh -server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -verbose:gc
====================

Bootup time need for JBoss as below (pure JBoss without any other apps in JBoss)
Sun Fire T5120(4 cores, 32 threads, 1.2Ghz) == 1m 20s
Sun Fire T2000(6 cores, 24 threads, 1.0Ghz) == 1m 54s
Sun Fire V440 (2 cores, 2 threads, 1.6Ghz) == 54s

Customer tested the boot up time for their Wintel server is far more faster than our Sun CMT processor server.

Customer unable to migrat their current test app into JBoss to do a load test due to their company policy.

Tuning for adjusting d heap, GC but boot up time still unacceptable.

I'm here seek for anyone who implemented their JBoss into Sun CMT processor server like T2000,T5120,T5220... can give me light up regarding their JBoss boot up time & wil JBoss multithreaded while in load test (runtime compilation)?

Thank you very much.

[peterj]

The problem is with either:

a) the operating system - Windows tends to let processes run full speed, some other operating systems, however, throttle back processes so that they do not use up all of the processing power. I do not know if the Sun Fire does this, but it is worth looking into.

b) disk speeds - slower disks will cause longer start-ip times, but not as much as you are reporting, so I would not think this is the issue

c) the JVM - there could something that the JVM is doing that is causing the slow startup. Considering that Sun makes Sun Fire and the JVM that runs on it, I would be surprised if this is the case. But stranger things have happened.

I suggest you ask Sun why their hardware or JVM is so slow.

[daniel.celentano]

We have same problem with a Sun T2000. We're lost with it. If you found a solution let me know.
tks.
Daniel

[gozilla]

This is a known characteristic of the T1 processor. It is slow for single threaded apps.

And the boot of JBoss is essentially single threaded. They are working on it.

If you want to boot your JBoss fast, you have to go for the fastest single threaded processor, like Intel P4 Extreme or AMD 3G+ equivalent. UltraSparc IV+ or 64 are not bad too, but still behind.

But when it comes to real life applications, when parallelism comes into play, the T1 is not bad, due to it's zillions cores :-)

HTH,
Francois