Hope this helps make things a bit clearer:
Concurrent users: 100
Concurrent requests (worst case): 100
Concurrent writes: 1-2 per request
Application: online quiz
Data written: small updates (100 bytes, approximately)
Thanks... I am just looking for some rough guidelines.
On Wed, Dec 16, 2009 at 6:58 PM, Andreas Jung <li...@zopyx.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 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.
> You have to provide much more details like #concurrent users,
> #concurrent requests, #concurrent writes, reads, the nature of the
> kind of data etc.
> - -aj
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
Zope3-users mailing list