> that OS can borrow some from your index. This swapping comes with price,
> which can or cannot be ok for you.
>
>
>
> - Original Message
>
>> From: Otis Gospodnetic
>> To: java-user@lucene.apache.org
>> Sent: Thursday, 23 July, 2009 18:55:5
other things, so that OS can
borrow some from your index. This swapping comes with price, which can or
cannot be ok for you.
- Original Message
> From: Otis Gospodnetic
> To: java-user@lucene.apache.org
> Sent: Thursday, 23 July, 2009 18:55:57
> Subject: Re: Loading an
009 9:47:24 AM
> Subject: RE: Loading an index into memory
>
> The size is in bytes and the RAMDirectory stores the bytes in bytes, so size
> is equal. I would suggest to not copy the dir into a RAMdirectory. It is
> better to use MMapDirectory in this case, as it "swaps" the f
Thank you both.
> Date: Thu, 23 Jul 2009 11:55:58 -0400
> Subject: Re: Loading an index into memory
> From: erickerick...@gmail.com
> To: java-user@lucene.apache.org
>
> What are you trying to accomplish? I'd insure that my performance wasa
> problem before doing an
What are you trying to accomplish? I'd insure that my performance wasa
problem before doing anything. If you're thinking "it's in RAM so it
has to be faster" you might be surprised.
So gather evidence that you have a problem before you jump to
providing a solution.
Erick
On Thu, Jul 23, 2009
The size is in bytes and the RAMDirectory stores the bytes in bytes, so size
is equal. I would suggest to not copy the dir into a RAMdirectory. It is
better to use MMapDirectory in this case, as it "swaps" the files into
address space like a normal OS swap file. The OS kernel will automatically
swa
