On Fri 05 Nov 2004, IvorW ivorw-openguides@xemaps.com wrote:
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.
It's spending a negligible amount of time in everything apart from that one statement with the regex in. A single search on "pub" spends *over eleven seconds* there.
How big a result set are these back-ends returning?
For a search on "pub" - almost 300. They return what they've been asked for, which is every page with that word in.
That's fine in itself; the problem is that the "super"search then hunts through each and every one of these using a regex to score them - and create a summary for each one, regardless of whether or not it's needed for the current page of results.
Hope this helps,
There's no help for a mess like this but to rewrite it from scratch. I can only apologise to everyone for having failed to properly supervise this part of the code. Hopefully Dom will keep a sharper eye on his developers... :)
Kake