Hi All,
I just noticed that the undo tab on our zopeserver takes ages to load.
If I try to trace the zope proces (as far as possible), it looks asif
the entire Data.fs is scanned.
Does zope scan the entire ZODB for old versions? It slows down our server
enourmously with a 3G Data.fs. If so,
On Thu, 2 May 2002 12:32:33 +0200, Ivo van der Wijk [EMAIL PROTECTED]
wrote:
I just noticed that the undo tab on our zopeserver takes ages to load.
If I try to trace the zope proces (as far as possible), it looks asif
the entire Data.fs is scanned.
It scans back as far as it needs to find
ZPsycopgDA (for postgres) is definitely multi-threaded. I think zPopyDA is
too.
Another solution might be to setup your site using ZEO and several single
threaded ZEO Clients. Then put a load balancer in front of it. Then the
single-threadedness is much less of an issue, since you have
In Zope 2.3.3 we did this with ZCatalog, on a field index:
query['effective_date'] = ['', DateTime.now()]
query['effective_date_usage'] = 'range:max'
This returns all records where the effective_date is lower than todays date
OR the effective_date is an empty string.
In
- Original Message -
From: Lennart Regebro [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 02, 2002 10:48
Subject: [Zope-dev] range:max, date times and pluggableindexes
In Zope 2.3.3 we did this with ZCatalog, on a field index:
query['effective_date'] = ['',
On Thursday 02 May 2002 10:48 am, Lennart Regebro allegedly wrote:
In Zope 2.3.3 we did this with ZCatalog, on a field index:
query['effective_date'] = ['', DateTime.now()]
query['effective_date_usage'] = 'range:max'
This returns all records where the
On Thu, 2 May 2002, Toby Dickenson wrote:
and all of them are eligible to be shown on the page. However if you
are looking at the undo tab of an insignificant leaf object that
rarely changes, it might have to scan through a very large number of
transactions before it finds 20 relevant ones to
Smells like a bug. Maybe try to use record-style parameters instead the
usage of old-style parameters (described in the Zope Book).
I did that, and it made no difference. I've also dug some more and tested a
lot, and figured out the problem:
Strings are always evaluates as larger than
--On 02 May 2002 10:08 -0400 Casey Duncan [EMAIL PROTECTED] wrote:
ZPsycopgDA (for postgres) is definitely multi-threaded. I think zPopyDA
is too.
http://www.zope.org/Members/glpb/solaris says:
The report also investigates in a cursory way the effects of adding a
database adapter to the
REQUEST FOR URGENT BUSINESS ASSISTANCE
--
Your contact was availed to me by the chamber of
commerce. It was given
to me because of my diplomatic status as I did not
disclose the actual
reasons for which I sought your contact. But I was
assured
That you are
Thanks for the info guys. It looks like these might do the trick.
-Original Message-
From: Paul Browning [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 10:55 AM
To: Casey Duncan
Cc: Jeff Nielsen / UgoFast; zope-dev
Subject: Re: [Zope-dev] Threaded Database Access
--On 02
11 matches
Mail list logo
