Tim Peters wrote:
[Seb Bacon]
But main the reason I'm posting is to wonder if there any reason not
to use the multiunion operator instead of the union operator in
UnIndex.py... it should be faster, right? It seems a touch faster in
some informal tests.
[Casey Duncan]
Yes, it probably should
Casey Duncan wrote:
On Thu, 06 Nov 2003 19:11:55 +
Seb Bacon [EMAIL PROTECTED] wrote:
A simple query for [A or B or C] against a KeywordIndex containing
27k objects is taking about 7 seconds on a Celeron 1.6Ghz, which seems
an absurdly long time to me.
guess
This time may be caused by
On Fri, 07 Nov 2003 12:02:07 +
Seb Bacon [EMAIL PROTECTED] wrote:
Casey Duncan wrote:
On Thu, 06 Nov 2003 19:11:55 +
Seb Bacon [EMAIL PROTECTED] wrote:
A simple query for [A or B or C] against a KeywordIndex containing
27k objects is taking about 7 seconds on a Celeron 1.6Ghz,
Casey Duncan wrote:
guess
This time may be caused by fetching from the database. If so, then the
only way to speed it up is increase the ZODB cache or get faster disks.
Try the former and see if it helps. /guess
Upping the cache speeds it up to something sane.
However, I don't understand why.
On Thu, 06 Nov 2003 19:11:55 +
Seb Bacon [EMAIL PROTECTED] wrote:
A simple query for [A or B or C] against a KeywordIndex containing
27k objects is taking about 7 seconds on a Celeron 1.6Ghz, which seems
an absurdly long time to me.
guess
This time may be caused by fetching from the
[Seb Bacon]
But main the reason I'm posting is to wonder if there any reason not
to use the multiunion operator instead of the union operator in
UnIndex.py... it should be faster, right? It seems a touch faster in
some informal tests.
[Casey Duncan]
Yes, it probably should be used. I think
