connection cache is the number of objects cached in each zodb connection, its not directly correlated to threads except that each thread get its own connection for the course of a request, as a rough guide i would suggest working up from a size of 5k for the connection cache.. if an object is not in cache zope needs to load it at run time from the zodb. connections are managed as a lifo stack to maximize cache effectiveness. generally, running more threads is really not going to increase throughput unless the threads are blocking, for example on long running external database connections. running more threads than the hard set limit of 7 connections is also of questionable value as the thread will sleep on a lock till it can get a connection. hope that helps, -kapil On Fri, 2004-03-26 at 21:20, Dennis Allison wrote:
Does the size of the connection cache need to grow when Zope runs more threads. I currently am running 8 threads (default 4). I note that the current OODB connection cache size is FIXED at 7. Do I need to increase the size? I would have guessed the connection cache should be somewhat larger than the number of threads and that it should be set dynamically. Can anyone hazard a guess as to what it should be? twice the number of threads? more?
I am running Zope 2.6.3b2 but I think the same question is relevant for all versions of Zope.
_______________________________________________ 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 )