[jsword-devel] A thought on search indexing.

Mark Goodwin goodwinster at gmail.com
Mon Aug 23 14:51:44 MST 2004


On Mon, 23 Aug 2004 17:38:34 -0400, DM Smith <dmsmith555 at yahoo.com> wrote:
> I agree that it is too slow. I have put a line item into bugs.txt for
> it. My thought was that we would do it in the background (low priority)
> as part of the install rather than waiting until they search for the
> first time.

Ah yes, bugs.txt; I should read it before I post...

> I like your idea, but we may want to wait until after 1.0 because I
> think we should spend some time looking at it to see if we can optimize
> it. I have cut the time significantly already, but I think it can be faster.

Do you know of any (good) free profilers?  I had Jprobe for a bit at
work, but I can't afford it for home use.

> Another problem I have and I think Random J. User will have is that the
> first search seems to promise that there will be a result after the
> index is built. But no, they have to submit the search again.

Oh, yes, I forgot about that one..

> Also, I once got frustrated with the indexing (when it was really slow)
> and killed it. It left junk on my machine, and the program thought it
> had a valid index. The only way I could fix the problem was to delete
> the index. I had to read the code to determine where it was and what it
> was called.

This has happened to me once before too.  I've also had a problem with
corrupt search indexes *after* generation.  I never got to the bottom
of why though.


More information about the jsword-devel mailing list