[sword-devel] CLucene Indexes

[Troy A. Griffitts]

Dear Ian,

Are you using the latest version of SWORD from SVN along with its 
clucene integration (and the latest version of clucene)?  We had done 
some work to optimize index creation.  It shouldn't take anywhere near 1 
minute on a desktop system.  We've talked about distributing indexes in 
the past, but there are a number of down sides (indexes are related to 
the version of the engine you are using, not the version of the module-- 
due to the engine deciding of different fields to create in the doc for 
new features, etc.; indexes would have to be compatible between jsword 
and sword, which I believe they are not exactly compatible right now 
(because we index different items); etc.)  If you freeze your app to a 
specific sword engine version and clucene version, then you could 
provide the indexes from another site which your app could download when 
the user chose to download a module (your option 3).

But, I would first like to work on optimizing the index build times.

	-Troy.



Ian Wagner wrote:
> Hello all,
> 
> I have determined that using CLucene is going to be the fastest way to  
> do searching with the iPhone frontend. Search times are very fast once  
> the indexes have been built. The problem that I am facing now is the  
> time required to index a module. In the simulator, the device  
> apparently has the same power as my macbook's CPU and consequently  
> builds the index in about a minute, which is bearable for a one-time  
> operation and could even be done in the background. When I tried the  
> operation on my iPod Touch, the operation took 20 minutes on the ESV  
> module, which is obviously unacceptable. I can think of 3 solutions to  
> the problem at the moment: 1) Distribute the indexes with the modules  
> in the repository. This would be nice because frontends could take  
> advantage of CLucene's indexing without having to do the time- 
> consuming index operation. On the other hand, it would require someone  
> indexing all of the modules, updating the repository, and adding a  
> couple megs onto each module that some frontends might not use. Option  
> 2) I could setup my own repository for indexed modules that the iPhone  
> frontend would download from, but I think there are some licensing  
> issues with that if I'm not mistaken. Option 3) I setup a repository  
> from which to download the lucene indexes. I think that the third  
> option would be best, but I would like to hear everyone's thoughts on  
> this issue.
> 
> Ian
> ---------------
> There's no place like 127.0.0.1
> 
> 
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page