[Zope] Performance and Server Requirements

Chris McDonough chrism@digicool.com
Thu, 19 Apr 2001 12:12:56 -0400


Maybe.  It depends on the application.  An application that makes heavy use
of dynamicism via DTML and/or PythonScripts might not be served adequately
by a single box.  Likewise, an application which makes heavy use of a
single-threaded database adapter may not be suited for this configuration
either.

I'd recommend that anyone facing serious load (and 10,000 hits/day is not
insane traffic, but it's not really tiny either) consider starting out with
ZEO and profile their application heavily before putting it into production.
ZEO is an escape hatch here.


----- Original Message -----
From: "Chris Gray" <cpgray@library.uwaterloo.ca>
To: <zope@zope.org>
Sent: Thursday, April 19, 2001 12:03 PM
Subject: Re: [Zope] Performance and Server Requirements


> OK, so a site that's only in the tens of thousands of hits per day range
> should be no sweat.  What about the Linux server to put under it?  Am I
> wrong to think that a single processor and 256meg should do the trick?
>
> Chris
>
>
> On Thu, 19 Apr 2001, Chris McDonough wrote:
>
> > Rough rule of thumb is that raw Zope can handle from between 40 - 80
hits
> > per second on a single simple page (depending on hardware).  This is
about
> > as fast as it's going to go.
> >
> > Complicated DTML or Python can slow this down dramatically.  You'll need
to
> > do profiling on your application to understand where your boundaries
are.
> > Some applications give an effective per-second hit rate of 20 hps, where
> > others creak along at 1hps.  We've had luck using an open source load
> > testing package named OpenSTA to do profiling.  Zope also ships with its
own
> > interface to the Python code profiler, which can let you determine where
in
> > your application you're spending most of the time.
> >
> > Using ZEO, you can scale the number of read requests per second almost
> > linearly.  So for example, if you have an application which has
performance
> > characteristics of 20 readsonly-hits-per-second on a single non-ZEOd
Zope,
> > you can usually estimate that you can serve ~ 40
readonly-hits-per-second on
> > a two-client ZEO cluster.  Give it three and you can do 60, etc.
> >
> > Things get a little murkier if there's lots of writes going on.  Again,
in
> > this situation, its best to do profiling.
> >
> >
> > ----- Original Message -----
> > From: "Chris Gray" <cpgray@library.uwaterloo.ca>
> > To: <zope@zope.org>
> > Sent: Thursday, April 19, 2001 11:35 AM
> > Subject: [Zope] Performance and Server Requirements
> >
> >
> > >
> > > I'm looking for information on Zope performance and server hardware
needs.
> > > I need info on what size of site and volume of traffic can be handled
by
> > > Zope and at what point it is recommended to go up to ZEO.  I'd also
like
> > > good recommendations on specs for a Linux server to host a Zope Web
site.
> > >
> > > Thanks,
> > > Chris
> > >
> > >
> > > _______________________________________________
> > > Zope maillist  -  Zope@zope.org
> > > http://lists.zope.org/mailman/listinfo/zope
> > > **   No cross posts or HTML encoding!  **
> > > (Related lists -
> > >  http://lists.zope.org/mailman/listinfo/zope-announce
> > >  http://lists.zope.org/mailman/listinfo/zope-dev )
> > >
> >
>
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )
>