----- Original Message ----- From: "Kake L Pugh" kake@earth.li To: "OpenGuides software developers" openguides-dev@openguides.org Sent: 02 November 2004 20:30 Subject: Re: [OpenGuides-Dev] supersearch.cgi disabled
... I profiled the search and found out that the reason it's so inefficient is that it's basically ignoring all indexing and doing the search with a regex!
That's interesting. You've done some profiling to show that the code is not spending the majority of its time in Plucene or SII.
How big a result set are these back-ends returning?
The original idea was that they return only a set of candidate pages which could satisfy the search, and the regex does the syntactic fine filtering on this.
Iterating the parse tree and regexen was only designed to be run on a very small subset of the wiki pages - the returned candidate matches.
If the backend searches are returning large result sets, this could explain the problem.
Hope this helps,
Ivor.