🚀 go-pugleaf

This isn't an answer but is I note I wrote up on the subject...


As you may know Sun released jdk1.2.2 for Linux. What Sun they failed to

credit was it was really just blackdown's version with a touch up by
Inprise.  As such it's a rev or so behind blackdown's version and lacks
some things like native threads.

Today I sat down with Apache's JMeter (great little load tester) and
beat the hell of some of our servers. It was a simple test - pulling a
page from a servlet running under Jetty2.3.3. The page reports various
statistics so it does a some computation and then some formatting. So
its not a complex test but not trivial. I tested this page under three
configurations:

(1)   blackdown's jdk1.2.2 rc3  w/ native threads
(2)   blackdown's jdk1.2.2 rc3  w/ green threads
(3)   sun/inprise's jdk1.2.2 rc1  w/ green threads

The three  machines I tested on were all pentium II 300 MHz or better w/

128 MB memory and 2.2.13 kernels.  The numbers varied on the different
machines but the relative performance of the three configurations on
each box was about the same. JMeter was using 10 threads with a random
delay with a guassian distribution and and average delay of 300 ms and
deviation of 100.

Response times leveled off to an average around:

    Config 1: 86 ms
    Config 2: 120 ms
    Config 3: 50 ms

Not: Configs 1 & 2 never really stabilized, exhibiting minor "seize ups"

periodically.

Blackdown has done amazing work and Java on linux wouldn't be be alive
without it but ... in production I'm running Sun/Inprise.