And a giveaway: Use StringBuffers. Check for log.isDebugEnabled(). Especially in loops. In May, this speeded up our application from 1s to 0.1s for certain pages (a speedup of euh... has anyone studied advanced math? ;) )
tomK > -----Original Message----- > From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]] > Sent: vrijdag 30 november 2001 18:51 > To: [EMAIL PROTECTED] > Subject: RE: Cocoon 2.0 Scalability Disappointment > > > >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). > > Cheers > Gerhard > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
