W3C home > Mailing lists > Public > www-jigsaw@w3.org > May to June 2000

Jigsaw 2.0.3 and performance problems

From: Ani Deglurkar <ani.deglurkar@commerceone.com>
Date: Tue, 6 Jun 2000 03:05:14 -0400 (EDT)
Message-ID: <393CA300.C54618A@commerceone.com>
To: www-jigsaw@w3.org
Hi all,

We use the Jigsaw 2.0.3 version to act as a web server in our product.
During a recent benchmark we observed that Jigsaw was not "calling" into
our servlet quickly enough and creating a bottleneck.

This was observed by running the performance monitor tools on NT. The
benchmark was running on a 8 CPU machine(NT) and all the CPUs were never
completely utilised. The max. that all the CPUs went to was 35-40%.
Increasing the incoming load/connections only made their response time
worse. But, the CPU load pattern did not change. There seems to
"serialising" that is happening.

Any ideas or suggestions would be appreciated? Are there any Jigsaw
2.0.3 performance numbers somewhere? I found some very old numbers on
the website, but they dated as far back as 97-98.

I am enclosing the socketclientfactory settings that we have used. I
tried to make the settings so that the Jigsaw server would not try to
change any thread priorities while running.  The max. number of
simultaneous connections went from 20 to 40 to 100.




# refer # to


#30 % of above
#70% of above

#70 % of maxClients

#idletimeout should be about 5 minutes or so
Received on Tuesday, 6 June 2000 04:24:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:36 UTC