cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Froehlich" <>
Subject RE: Cocoon 2.0 Scalability Disappointment
Date Fri, 30 Nov 2001 17:50:46 GMT
>1) disable logging. If log is DEBUG, it could generate Gigabytes of
>information and disks could become the bottleneck.
>[I think log might be the bottleneck]
>2) disable resource reloading. Same as above, the disk I/O system could
>become the bottleneck.
>3) try to come up with some logarithmic stress tests: 1 req/sec, 2
>req/sec, 4 req/sec, 8, 16, 32, 64, until your machines saturate.
>4) turn the cache off/on. [this, compared to the logaritmic approach
>should give us information on the caching system]
>5) try to get the generated source code of one of your XSP, compile it
>as a generator and use it as a normal generator instead. [this should
>remove the XSP loading/handling phase]

6) Look at the store parameters (store,store-janitor,...) in the 
cocoon.xconf file and customize them -as recommended in the comments- for 
your testing machine(s).


To unsubscribe, e-mail:
For additional commands, email:

View raw message