[sword-devel] module modtime -vs- CLucene index out-of-date-ness
dmsmith555 at yahoo.com
Wed May 2 13:54:21 MST 2007
Chris Little wrote:
> Unfortunately, that's impractical. With a virus scanner on, the
> compression takes 5 minutes for a single Bible (OT+NT) on my Win32
> system (2GHz Pent-M, 7200RPM drive), due to the constant disk access. We
> would either have to tell users to disable virus protection or deal with
> people complaining that their systems freeze every time they add/update
> a module.
Actually, Lucene has an implementation of a RamDirectory to which the
index can be written. And once completed it can be copied to the local
file system. We've done it in JSword and the results were phenomenal. I
presume that the CLucene implementation is sufficiently similar to
Lucene to have it. It is less than 10 lines of additional code in Java.
The only problem is that it eats RAM proportional to the size of the
final index. I have not measured it to see how big it is, but since
Win98SE with all the updates on an old Pentium laptop is hardly usable
with less than 64M RAM, I think that most machines have enough RAM.
After ugrading my old laptop to 128M ram, JSword can index in about 4
minutes, whereas I never had the patience to let it complete before.
That aside, it shifts from being disk bound to cpu bound and the machine
is still practically unresponsive. So I think that it will still be
> Kahunapule Michael Johnson wrote:
>> What about updating the Sword engine to index each module as it is
>> installed, if the indexing can be used. That way, you get small
>> downloads for everyone, faster searches for those who can use indexes,
>> and a little more module installation time.
>> Just a thought...
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel