Hello,
I'm using Lucene 3.4.0 and I would like to create a custom file with each
segment file Lucene creates (without modifying the source code).
I managed to create a custom indexing chain to create my file (e.g. _0.map,
_1.map ...) and it works!
I also created a custom IndexWriter to override
Hello everyone,
We have a performance issue ever since we stopped optimizing the index. We are
using Lucene 4.8 (jvm 32bits for searching, 64bits for indexing) on Windows
2008R2.
Now we are letting Lucene handle the merges using the default merge policy
(TieredMergePolicy).
We have narrowed do
iginal Message-
From: Toke Eskildsen [mailto:t...@statsbiblioteket.dk]
Sent: samedi 17 mai 2014 20:04
To: java-user@lucene.apache.org
Subject: RE: search time & number of segments
De Simone, Alessandro [alessandro.desim...@bvdinfo.com] wrote:
> We have a performance issue ever since we stopped optimiz
iginal Message-
From: Toke Eskildsen [mailto:t...@statsbiblioteket.dk]
Sent: lundi 19 mai 2014 16:43
To: java-user@lucene.apache.org
Subject: Re: search time & number of segments
On Mon, 2014-05-19 at 11:54 +0200, De Simone, Alessandro wrote:
[24GB index, 8GB disk cache, only indexed fields]
&
ig impact on
performance.
-Original Message-
From: Toke Eskildsen [mailto:t...@statsbiblioteket.dk]
Sent: mardi 20 mai 2014 15:46
To: java-user@lucene.apache.org
Subject: Re: search time & number of segments
On Tue, 2014-05-20 at 15:04 +0200, De Simone, Alessandro wrote:
Tok
i 2014 22:09
To: java-user@lucene.apache.org
Subject: RE: search time & number of segments
De Simone, Alessandro [alessandro.desim...@bvdinfo.com] wrote:
> We have stopped optimizing the index because everybody told us it was a bad
> idea.
> It makes sense if you think about it. When
Hi!
We have switched from Lucene 3.6 to >=Lucene 4.7 (java7) and we are also
experiencing a distinct slowdown using the same dataset. We are running the
software under Windows 2008R2.
In our case, we have identified that there a lot more IO calls (= number of
time the buffer is refilled in Ind
