see http://jakarta.apache.org/lucene/docs/contributions.html
LUKE is a stand alone application for viewing and querying an index
LIMO is a web application for monitoring the content of an index
- Original Message -
From: Ian McDonnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday,
luke once its been added to the classpath on Tomcat? I
cant seem to find any docs on the luke site.
Ian
--- Julien Nioche [EMAIL PROTECTED] wrote:
see http://jakarta.apache.org/lucene/docs/contributions.html
LUKE is a stand alone application for viewing and querying an index
LIMO is a web
It is not surprising that you run out of file handles with such a large
mergeFactor.
Before trying more complex strategies involving RAMDirectories and/or
splitting your indexation on several machines, I reckon you should try
simple things like using a low mergeFactor (eg: 10) combined with a
application.
The index used for this test is 720 MB - FSDirectory on Fedora 1
the .tii file is 3398 Kb in the modified version against 488Kb in the
original (INDEX_INTERVAL=128)
Has anyone tried changing this value? Do you get similar results?
Julien
- Original Message -
From: Julien
Has anyone tried comparing the performance of regular (multi-file) indexing
and specifying a value for minMergeDocs?
Using parameter limits the number of files and is supposed to improve the
speed of indexation.
- Original Message -
From: Otis Gospodnetic [EMAIL PROTECTED]
To: Lucene
Or set a big value with minMergeDocs on IndexWriter and keep a low
mergeFactor (ie 10). You'll have a small number of files on your disk and
the indexing should be faster as well.
- Original Message -
From: Matt Quail [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent:
Joachim,
Why don't you use the method explain of IndexSearcher?
http://jakarta.apache.org/lucene/docs/api/org/apache/lucene/search/IndexSear
cher.html
This is the best way to find why your documents are different. I suspect the
lengthNorm method, which is used at indexation time.
Julien
There's a new release of limo available !
This new version :
- includes lucene-1.3-final.jar
- fixes a bug with index loading
- detects when index changes and auto refreshes the information (as proposed
by Jakob Flierl)
- uses css for easier customisation (as proposed by E Hatcher)
- escapes HTML
Hello,
Since there are a lot of Term objects in your Query, your application must
spend a lot of time collecting information about those Terms.
1/ Do you use RAMDirectory? Loading the whole Directory into memory will
increase speed - your index must not be too big though
2/ You are probably not
.
Any comments would be appreciated
Best regards
Julien Nioche
http://www.lingway.com
-- Debut du message initial ---
De : fp235-5 [EMAIL PROTECTED]
A : lucene-dev [EMAIL PROTECTED]
Copies :
Date : Sat, 20 Sep 2003 16:06:06 +0200
Sujet : [PATCH] IndexWriter
Hello,
Thanks to Andrzej for this new version! Luke is really useful.
open the original Dokuments with the platform dependant mimetype viewer
???
My suggestions by order of importance would be :
- History of the 5 last indexes used : under the File Menu item ?
- Remove the empty field (see
(www.lingway.com) for more information about
our activities.
Thank you
Julien Nioche / www.lingway.com
12 matches
Mail list logo