I'd say put a small benchmark together that does the expected load and
see which config performs better.
I guess on the short run it's easier to get by with a single
FileStorage and multiple threads, but on the long run maybe with more
Wednesday, December 16, 2009, 2:32:35 PM, you wrote:
RM> Hope this helps make things a bit clearer:
RM> Concurrent users: 100
RM> Concurrent requests (worst case): 100
RM> Concurrent writes: 1-2 per request
RM> Application: online quiz
RM> Data written: small updates (100 bytes, approximately)
RM> Thanks... I am just looking for some rough guidelines.
RM> On Wed, Dec 16, 2009 at 6:58 PM, Andreas Jung <li...@zopyx.com> wrote:
RM> -----BEGIN PGP SIGNED MESSAGE-----
RM> Hash: SHA1
RM> schrieb Roy Mathew:
>> Folks, I am looking for some configuration advice.
>> I am running a zope3 application that uses the ZODB. I expect a
>> peak load of a 100 concurrent users, and am on a *quad* core Intel
>> Xeon Linux box. Am I better off running 2 or 3 ZEO clients talking
>> to the app-server (I am assuming that the OS will load balance so
>> that all processors are utilized well). Or should I not use ZEO at
>> all, and simply assign a large cache, a large connection pool and
>> lots of threads to a single process. I am sure that this is an
>> issue many of you have had to contend with. I would appreciate some
>> rough idea of what the numbers should be for each of the 2
>> scenarios I outline.
RM> You have to provide much more details like #concurrent users,
RM> #concurrent requests, #concurrent writes, reads, the nature of the
RM> kind of data etc.
RM> - -aj
RM> -----BEGIN PGP SIGNATURE-----
RM> Version: GnuPG v1.4.10 (Darwin)
RM> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
RM> -----END PGP SIGNATURE-----
Adam GROSZER mailto:agros...@gmail.com
Quote of the day:
True humility is not an abject, groveling, self-despising spirit; it is but a
right estimate of ourselves as God sees us.
- Tryon Edwards
Zope3-users mailing list