t; Gudrun
>
>
> -Ursprüngliche Nachricht-
> Von: Shai Erera [mailto:ser...@gmail.com]
> Gesendet: Mittwoch, 14. Mai 2014 16:49
> An: java-user@lucene.apache.org
> Betreff: Re: best choice for ramBufferSizeMB
>
> Well, first make sure that you set ramBufferSizeMB to
.
Gudrun
-Ursprüngliche Nachricht-
Von: Shai Erera [mailto:ser...@gmail.com]
Gesendet: Mittwoch, 14. Mai 2014 16:49
An: java-user@lucene.apache.org
Betreff: Re: best choice for ramBufferSizeMB
Well, first make sure that you set ramBufferSizeMB to well below the max Java
heap size, otherwise
Is this true as well for 2.9.2?
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Wednesday, May 14, 2014 8:54 AM
To: Lucene Users
Subject: Re: best choice for ramBufferSizeMB
Generally larger is better, as long as JVM's heap is big enough to all
Hi all,
we want to speed up building our lucene index. We set ramBufferSize to some
values between 32 and 128 MB, but that does not make any difference concerning
the time used for reindexing. We did not set maxBufferedDocs, .. which could
conflict.
We start the JVM with the following JAVA_OPT
Generally larger is better, as long as JVM's heap is big enough to
allow IW to use that RAM.
Large flushed segments means less merging later ...
Mike McCandless
http://blog.mikemccandless.com
On Wed, May 14, 2014 at 9:33 AM, Gudrun Siedersleben
wrote:
> Hi all,
>
> we want to speed up buildin
Well, first make sure that you set ramBufferSizeMB to well below the max
Java heap size, otherwise you could run into OOMs.
While a larger RAM buffer may speed up indexing (since it flushes less
often to disk), it's not the only factor that affects indexing speed.
For instance, if a big portion o
