Performance and scalability of Jigsaw

Anselm,

We tested the performance of Jigsaw upon simultaneous
transactions againt Netscape, Apache and Jeeves.

Our conclusion is that Jigsaw is right now not very scalable.
For instance, with the Stresser utilitity provided in the 
distribution of Jigsaw we see the following results.

For Jigsaw with par = 10:

Total request: 411
Total time   : 61328
Req/sec      : 6.7016697104096
detailed results:
http://saggitaire:8001/: s=1046 t=1.4779268292682928 f=0 t=605950 c=410

For Apache with par = 10:

Total request: 2694
Total time   : 60157
Req/sec      : 44.78281829213558
detailed results:
http://saggitaire:80/: s=523 t=0.22259041960638695 f=0 t=599436 c=2693

For Jigsaw with par = 100:

Jigsaw crashed with the following exceptions,
client-5: caught ClientException: [w3c.jigsaw.http.ClientException]
Resource temporarily unavailable
[http-server] failed to accept incoming connection on
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8001]
[http-server] linux/193.106.58.164 refused (overloaded).


For Apache with par = 100:

Total request: 2957
Total time   : 65434
Req/sec      : 45.1905737078583
detailed results:
http://saggitaire:80/: s=523 t=1.6727302182810366 f=24 t=4904445 c=2932


Could you please comment on that.
I mean do you have suggestions on solutions to this scalability issue.
I really find Jigsaw a fantastic product.
My only concern right now is its scalability.

Francois



-- 

Sincerely yours,

-------------------------------------------------------
Francois Deza          mailto:francois.deza@sema.fr
Corporate R&D          http://www.semagroup.com  

Sema Group                tel:   33 - 1 - 40 92 43 16
16, rue Barbes            fax:   33 - 1 - 40 92 42 41
92126 Montrouge Cedex   
France                    

secretary: Beth Gould
tel:       33 - 1 - 40 92 42 18
email:     beth.gould@sema.fr
-------------------------------------------------------

Received on Thursday, 20 February 1997 07:08:50 UTC