On Wednesday 22 January 2003 3:10 pm, Ivo van der Wijk wrote:
On Wed, Jan 22, 2003 at 11:57:20AM +0000, Toby Dickenson wrote:
1. Obviously, use fewer threads. Do you have a component that otherwise benefits from many threads?
No, except that the server is pretty heavy loaded sometimes, and multiple threads should improve responsiveness (right?)
Not if your machine is cpu-bound. You need enough threads to keep your cpu busy, but any more than that means each one gets a smaller share of the cpu, and a smaller share of the memory. All my Zopes have 1 or 2 worker threads.
2. If you have large immutable state that does not hold references to persistent objects, use application-specific code to share this state between threads.
Not really. The bloat is caused by a large squishdot site (20.000 comments)
That will really benefit from 2.6 and a bigger cache, as seb suggested. Fewer threads means you can have a bigger per-thread cache, for the same total memory usage. -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson