>From experience, one of the most efficient performance boosts is to
purchase a fast machine for it. If you're in a commercial environment,
your shareholders might prefer that you spent your costed time
developing new things instead of spending a few extra hundreds of
pounds/dollars on expensive CPUs. We even have a plone 2.0 site that
is quite fast believe it or not.
And yes, as J says, get the worst bottlenecks out of the way, but bare
in mind that it's only a bottleneck if it's requested often (such as
If you are relying on the Data.fs for complex data handling, make sure
that your common read methods don't make any writes to the zodb. I had
such a "bug" in the issuetrackerproduct where getIssueFiltered() made
a save to the zodb under certain conditions. Under heavy use I started
to get zodb conflict errors that I didn't see when developing on
On 8/31/05, J Cameron Cooper <[EMAIL PROTECTED]> wrote:
> Kennamore, Matthew G [NTK] wrote:
> > Here is our situation, we originally launched zope with a small user
> > base in mind and like most IT implementations it got away from us
> > quickly and we have over 1000 users now. We are experiencing huge
> > slowdowns and lots of complaints of performance.
> > Let me outline our system:
> > I have a load balancer that round robins incoming request to 3 zeo servers
> > I have 1 zope server on the back en that severs the data, this is a
> > large single processor machine with 4 gigs of ram
> > Each zeo server is 2 gigs of ram, single processor 3.2 gighz
> > The throughput doesn't appear to be the problem as ram/processors are.
> > Short term I plan to change all zeo's to 4 gigs ram and add 3 additional
> > servers.
> > The Technologies we are using are Zope, Zeo, plone and so forth. Why
> > are we having these large issues? I see sites with hundreds of
> > thousands of users and they don't seem to have these issues? We plan to
> > recode our site to get away from the Data.fs as soon as we can but that
> > is a ways off yet. What am I doing wrong can anyone help?
> You will need to find out where the slow bits are. There are various
> profiling tools for use in Zope. PTProfiler, CallProfiler, etc. Also
> examine your ZODB cache graphs and settings. These can tell you where
> your bottlenecks are.
> There are lots of ways to improve performance just administratively. You
> can improve various zope.conf settings, and set up caching (either RAM
> or HTTP Accel.) in Plone. You can also put a caching proxy server (like
> Squid) in front of your Zopes.
> Also, Plone 2.1 is significantly faster.
> "Building Websites with Plone"
> Enfold Systems, LLC
> Zope maillist - Zope@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-dev )
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -