How can i improve performance of website under heavy load in Zope2.6.1
Hi, I am using Zope 2.6.1 I wonder why Zope is default set for handling 4 threads and 7 database connections. I tried inreasing threads to 20 and database connections to 30 by updating z2.py and DB.py, presuming that this will help to improve performance under heavy load. Can anyone suggest what impact will be there if i do this , in Zope 2.6.1 OR Can anyone suggest any other option to improve performance under heavy load in Zope 2.6.1 Any help will be appreciated. Suson
1) improve the number of object in the cache: the default is 400 which is incredibly low for a normal site; put it to 5000 and check; 2) (if possible) upgrade to a newer release of Zope, namely 2.8, which removes many possible conflict, and therefore improves response time; 3) install a Zope/ZEO configuration, with more than one Zope server responding; don't mix too much with threads which is, as far as I know, tricky stuff; use more than one physical server, running Zope, connected to a ZEO backend; distribute the load using whatever load balancer of your choice; 4) review your application needs; check what are the actual bottlenecks; is there any static content you could better serve using apache (like images, documents..) ? 5) make a google search with "improving Zope performance" ;) Regards Marco On 7/31/06, Sudesh Soni <sudesh.soni@ebusinessware.com> wrote:
Hi,
I am using Zope 2.6.1
I wonder why Zope is default set for handling 4 threads and 7 database connections.
I tried inreasing threads to 20 and database connections to 30 by updating z2.py and DB.py, presuming that this will help to improve performance under heavy load.
Can anyone suggest what impact will be there if i do this , in Zope 2.6.1
OR
Can anyone suggest any other option to improve performance under heavy load in Zope 2.6.1
Any help will be appreciated.
Suson
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
-- Marco Bizzarri http://notenotturne.blogspot.com/
Sudesh Soni wrote at 2006-7-31 12:43 +0530:
I wonder why Zope is default set for handling 4 threads and 7 database connections.
Because these values are in general not too bad.
I tried inreasing threads to 20 and database connections to 30 by updating z2.py and DB.py, presuming that this will help to improve performance under heavy load.
Can anyone suggest what impact will be there if i do this , in Zope 2.6.1
You may drastically increase the RAM requirements of your Zope process: Each connection maintains its own (independent) ZODB cache. Main memory requirements therefore increases linearly with the number of connections.
... Can anyone suggest any other option to improve performance under heavy load in Zope 2.6.1
Cache whatever is cachable... -- Dieter
On 31. Jul 2006, at 09:13, Sudesh Soni wrote:
I wonder why Zope is default set for handling 4 threads and 7 database connections.
These are good values under normal circumstances.
I tried inreasing threads to 20 and database connections to 30 by updating z2.py and DB.py, presuming that this will help to improve performance under heavy load.
Can anyone suggest what impact will be there if i do this , in Zope 2.6.1
Zope is not Apache. Increasing the number of threads is unlikely to help performance unless, perhaps, when you have a heavily loaded RDBMS backing your Zope and see threads "hanging" waiting for the RDBMS to respond.
OR
Can anyone suggest any other option to improve performance under heavy load in Zope 2.6.1
Figure out why your Zope is slow. Is it CPU bound or I/O bound? Use a profiler to analyze your code (PTProfiler, ZopeProfiler). Set up ZEO + multiple ZEO clients, if need be on multiple boxes. And put a cache in front, Squid works well. Stefan -- Anything that, in happening, causes something else to happen, causes something else to happen. --Douglas Adams
participants (4)
-
Dieter Maurer -
Marco Bizzarri -
Stefan H. Holek -
Sudesh Soni