On 9/1/05, Kennamore, Matthew G [NTK] <[EMAIL PROTECTED]> wrote:
> Zope version 2.7.3 (planning to goto 2.7.7 soon with ZODB 3.2.9)
> Pyhton is 2.3.4
> Apache 1.3
>
> We have 943 users as of this minute with a bout 1000 objects being created a
> day (Lots of creates)
Interesting. Somebody have a
Andrew Sawyers wrote:
Did Matt indicate if he was running multiple zeo app servers? It might help
to be spreading the load. 1, writes a day is not outrageous
Yes, but he's using Plone, which implies not only all of the CMF
reindexing overhead, but also all the AT and Plone layers on
PM
To: Kennamore, Matthew G [NTK]; 'Chris McDonough'
Cc: zope@zope.org
Subject: RE: [Zope] Zope scalabilty and problems
Sorry,
I missed the beginning of this thread, I've got some questions that I didn't
see answered or asked:
Did Matt indicate if he was running
:[EMAIL PROTECTED] On Behalf Of
> Kennamore, Matthew G [NTK]
> Sent: Thursday, September 01, 2005 1:19 PM
> To: Chris McDonough
> Cc: zope@zope.org
> Subject: RE: [Zope] Zope scalabilty and problems
>
> Thanks everyone for their suggestions, bought a squid book today and I
> k
bject: RE: [Zope] Zope scalabilty and problems
What you've got now is a pretty reasonable setup. Moving to 2.7.7 will
likely not get you any "free" performance increases and it doesn't
appear that there are any "critical" ZODB bugfixes relating to your
pro
Zope version 2.7.3 (planning to goto 2.7.7 soon with ZODB 3.2.9)
> Pyhton is 2.3.4
> Apache 1.3
>
> We have 943 users as of this minute with a bout 1000 objects being created a
> day (Lots of creates)
>
> -Original Message-
> From: Chris McDonough [mailto:[EMAIL
, 2005 12:51 PM
To: Kennamore, Matthew G [NTK]
Cc: zope@zope.org
Subject: Re: [Zope] Zope scalabilty and problems
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
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
:Re: [Zope] Zope scalabilty and problems
> 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
Am Mittwoch, 31. August 2005 18:50 schrieb J Cameron Cooper:
> 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 fron
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 ditc
>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 CP
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 o
On 8/31/05, Kennamore, Matthew G [NTK] <[EMAIL PROTECTED]> 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 g
14 matches
Mail list logo
