On 8/31/05, Kennamore, Matthew G [NTK] <Matthew.G.Kennamore@sprint.com> wrote:

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?

Always hard to tell, but maybe you do many writes to the ZODB? As long as you only read Zope can be very fast, but writes to the ZODB will take a long time. Also, Plone (and any CMF technology in fact) has a serious performance hit in the skins system. There are some improvements possible there, like giving visitors a special skin that includes fewer skin folders and such. Check on a plone list for more help there. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

Kennamore, Matthew G [NTK] wrote:

The Technologies we are using are Zope, Zeo, plone and so forth. Why are we having these large issues?

It depends entirely on your application. Plone doesn't help you here, and I'd certainly consider replacing that long before I think about trying to ditch ZODB in favour of a relation back end (something I find confusing, since a relational db can be just as slow if you mistreat it in the ways people often mistreat ZODB - "Data.fs", ie: FileStorage, is about as fast as it gets when used correctly. As I said, Plone doesn't help you here, and it, and the coding styles it encourages, along with Archetypes myriad layers of indirection are likely to be the source of your problem. I'd start with: - make sure requests that shouldn't be writing to the ZODB aren't writing to the ZODB - The Undo tab in the root of your Zope instance is good for that, it shouldn't have any entries for views on it - get PTProfiler up and running and profile your most commonly used urls, try and knock on the top file slowest items on the profile results, or at least make them not slow anymore - look at doing some clever coding, portal_catalog search and AT references are the worst offendors for hopelessly slow code that you'd expect to be fast. - finally, start looking at app-level caching, things like CMF's cookedBody can be applied more widely as techniques. - at this point, look at systemic caching such as Squid, ESI, etc. This is much harder if you need to have authenticated users. cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

Your "tranaaction blocked" error messages seem to imply that either or both of the following is true: - some transactions are taking a "long time" (any more than, say, 200 milliseconds is a long time) - you have a very high transaction volume. That said, these messages are informational rather than signifying an error condition. Some transaction blockage is expected since the ZEO server can only deal with one transaction at a time. What version of Zope are you using? Is this an "intranet" application? Are there lots of users creating content? Can you venture a guess as to how many users are "creating" content vs. "viewing" content at any given time? Are the users that are creating content logged in? The users that are viewing content? On Wed, 2005-08-31 at 11:03 -0500, 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?

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )