On Sun, 2003-04-27 at 17:20, Tim Starling wrote:
> At the moment, all the search feature does is tells you there are no title
> matches (regardless of what you search for), and directs you to a Google
> search. The go button still works, so at the moment "go" is the only way
to
> do a title search. I had assumed the dev. team has this under control and I
> worked around it, but I've had a new user (Susurrus) complain directly to
> me, asking me to forward his complaint on to here. So here it is. I know
> about "miser mode", but this isn't miser mode, it's nonexistent
mode.
> What's going on?
I've just gone ahead and turned the title search
back on. I mean, heck,
who wants to actually be able to read or write anything on the wiki?
Much better to be able to search it -- _if_ you're lucky enough to get
through at all.
As I wrote you by private mail, I think people would be much more willing
to accept a temporary deactivation of the sysop SQL feature, which, if at
all, should be run on a separate machine (possibly a mirror, could really
be 1-2 days out of date).
As for the search itself, I would like to know *why* it is slow. A simple
title search should really cause no problems. Could it be that the search
is delayed by other factors? How fast is it when it is run without load?
Regards,
Erik