t; >> This is managed by your operating system. In general OS kernels like
>> Linux
>> >> or Windows use all free memory to cache disk accesses.
>> >>
>> >> -
>> >> Uwe Schindler
>> >> H.-H.-Meier-Allee 63, D-28213 Bremen
&
like
> Linux
> >> or Windows use all free memory to cache disk accesses.
> >>
> >> -
> >> Uwe Schindler
> >> H.-H.-Meier-Allee 63, D-28213 Bremen
> >> http://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>
> >
;> H.-H.-Meier-Allee 63, D-28213 Bremen
> >> http://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>
> >>
> >> > -Original Message-
> >> > From: Cheng [mailto:zhoucheng2...@gmail.com]
> >> > Sent: Monda
ee memory to cache disk accesses.
>>
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>
>> > -Original Message-
>> > From: Cheng [mailto:zhouc
hetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Cheng [mailto:zhoucheng2...@gmail.com]
> > Sent: Monday, June 04, 2012 6:10 PM
> > To: java-user@lucene.apache.org
> > Subject: Re: RAMDirectory unexpectedly slows
> >
cheng2...@gmail.com]
> Sent: Monday, June 04, 2012 6:10 PM
> To: java-user@lucene.apache.org
> Subject: Re: RAMDirectory unexpectedly slows
>
> Can I control the size of ram given to either MMapDirectory or
> ByteBufferDirectory?
>
> On Mon, Jun 4, 2012 at 11:42 PM, U
Can I control the size of ram given to either MMapDirectory or
ByteBufferDirectory?
On Mon, Jun 4, 2012 at 11:42 PM, Uwe Schindler wrote:
> Hi,
>
> If you are using MMapDirectory or this ByteBufferDirectory (which is
> similar to the first) the used RAM is outside JVM heap, it is in the FS
> cac
Hi,
If you are using MMapDirectory or this ByteBufferDirectory (which is similar to
the first) the used RAM is outside JVM heap, it is in the FS cache of the OS
kernel. Giving too much memory to the JVM penalizes the OS cache, so give only
as much as the App needs. Lucene and the OS kernel will
> What about the ByteBufferDirectory? Can this specific directory utilize the
> 2GB memory I grant to the app?
BBD places the byte objects outside of the heap, so increasing the
heap size is only going to rob the system IO cache. With Lucene the
heap is only used for field caches and the terms di
Please shed more insight into the difference between JVM heap size and the
memory size used by Lucene.
What I am getting at is that no matter however much ram I give my apps,
Lucene can't utilize it. Is that right?
What about the ByteBufferDirectory? Can this specific directory utilize the
2GB me
If you want the index to be stored completely in RAM, there is the
ByteBuffer directory [1]. Though I do not see the point in putting an
index in RAM, it will be cached in RAM regardless in the OS system IO
cache.
1.
https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/ap
My indexes are 500MB+. So it seems like that RAMDirectory is not good for
that big a size.
My challenge, on the other side, is that I need to update the indexes very
frequently. So, do you think MMapDirectory is the solution?
Thanks.
On Mon, Jun 4, 2012 at 10:30 PM, Jack Krupansky wrote:
> Fro
From the javadoc for RAMDirectory:
"Warning: This class is not intended to work with huge indexes. Everything
beyond several hundred megabytes will waste resources (GC cycles), because
it uses an internal buffer size of 1024 bytes, producing millions of
byte[1024] arrays. This class is optimi
13 matches
Mail list logo