[ZCM] [ZC] 1452/ 4 Comment "manage_catalogIndexes still very very slow with ZCTextIndex"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1452 Update (Comment) "manage_catalogIndexes still very very slow with ZCTextIndex"
 Status Pending, Zope/bug medium
To followup, visit:
  http://zope.org/Collectors/Zope/1452

==============================================================
= Comment - Entry #4 by Caseman on Aug 3, 2004 1:45 pm

Notice the comment above this line and line 86 of BaseIndex.py in the __init__() method. The length() method in the class is replaced by a callable Length object in the index index.

IMO this tries too hard to be clever. A reasonable change that might help understanding would be to have the length method raise NotImplementedError, since it is just a placeholder. Eliminating the method might be ok also, implicit acquisition notwithstanding.
________________________________________
= Comment - Entry #3 by ajung on Aug 3, 2004 1:12 pm

BaseIndex.length() calls len() on a BTree instead of using the value of the existing counter self.document_count
________________________________________
= Comment - Entry #2 by chrisw on Aug 3, 2004 12:33 pm

Just to note that ZCTextIndex is definitely the culprite here.

I deleted the index (which is all I wanted to do anyway ;-) and suddenly the indexes tab was back to being lightening quick.
________________________________________
= Request - Entry #1 by chrisw on Aug 3, 2004 12:29 pm

The Indexes tab of a ZCatalog will craaaawl if there's a ZCTextIndex in there which has a decent number of words indexed in it.

It think something in the indexes tab ends up doing a len of a very big BTree.

Commenting out the "# objects" column makes it lightning quick again.

What does that column actually show?
Why are ZCTextIndex's so slow in it?

This really needs fixing...
==============================================================