Thanks for the helpful replies; I was also curious: assuming that one has a cache of a certain size, is there a way to inspect it (ie: to see how full/empty it is, etc..) so one can tell how effective it is at runtime. It would beat repeatedly running benchmarks while varying the cache size.<br>
<br><div class="gmail_quote">On Wed, Dec 16, 2009 at 7:57 PM, Andreas Jung <span dir="ltr"><<a href="mailto:lists@zopyx.com">lists@zopyx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
schrieb Roy Mathew:<br>
</div><div><div></div><div class="h5">> Folks, I am looking for some configuration advice.<br>
><br>
> I am running a zope3 application that uses the ZODB. I expect a<br>
> peak load of a 100 concurrent users, and am on a *quad* core Intel<br>
> Xeon Linux box. Am I better off running 2 or 3 ZEO clients talking<br>
> to the app-server (I am assuming that the OS will load balance so<br>
> that all processors are utilized well). Or should I not use ZEO at<br>
> all, and simply assign a large cache, a large connection pool and<br>
> lots of threads to a single process. I am sure that this is an<br>
> issue many of you have had to contend with. I would appreciate some<br>
> rough idea of what the numbers should be for each of the 2<br>
> scenarios I outline.<br>
><br>
</div></div>The number of worker threads (and clients) basically depends on how much<br>
concurrent requests you have. Four worker threads can deal with 100<br>
requests/second<br>
when each request can be processed fast. Long running requests will<br>
block other<br>
requests...so you must measure how long a request takes in average..then<br>
you can do your own calculations. The cache size depends on various<br>
factors..<br>
you have to check the ZODB activity in order to perform fine-tuning.<br>
There is neither a golden bullet nor a recipe for the perfect<br>
setup...start with<br>
a common setup of two clients or so and see how far you can go...then<br>
adjust<br>
your parameters over time.<br>
<div class="im"><br>
- -aj<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (Darwin)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>
</div>iEYEARECAAYFAkso7jgACgkQCJIWIbr9KYxJuACgnSBYveX6o5s6405R4Q+U9i5M<br>
wg4AnjjM0wuytuDaWF0GEs5yF/DbPU+C<br>
=tzFb<br>
-----END PGP SIGNATURE-----<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Roy.<br>