deeMail: u...@thetaphi.de> -Original
Message-> From: wangzhijiang999 [mailto:wangzhijiang...@aliyun.com]> Sent:
Tuesday, July 01, 2014 9:17 AM> To: java-user> Subject: 答复：RE: RE: About lucene
memory consumption> > My application also meet this problem last year and
> -Original Message-
> From: wangzhijiang999 [mailto:wangzhijiang...@aliyun.com]
> Sent: Tuesday, July 01, 2014 9:17 AM
> To: java-user
> Subject: 答复：RE: RE: About lucene memory consumption
>
> My application also meet this problem last year and I researched on the code
&
My application also meet this problem last year and I researched on the code
and found the reason.
The whole process is as follow:
1. When using NRTCachingDirectory, it will use RAMDirectory as cache and
MMapDirectory as delegate. The new segment will be created in the process of
flush or merge
"Uwe Schindler";;
Date: Sat, Jun 28, 2014 05:41 PM
To: "java-user";
Subject: RE: RE: About lucene memory consumption
Hi,
how does your configuration for NRTCaching directory looks like. There are 2
constructor params, one of the maxMergeSizeMB the other one is maxCac
Hi,
how does your configuration for NRTCaching directory looks like. There are 2
constructor params, one of the maxMergeSizeMB the other one is maxCachedMB. If
you correctly close (or release in case of ReaderManager/SearcherManager) all
indexes, this should limit the memory use.
There is no
Hi,
The number of byte[] instances and the total size shows that each byte[] is
approx. 1024 bytes long. This is exactly the size used by RAMDirectory for
allocated heap blocks.
So the important question: Do you use RAMDirectory to hold your index? This is
not recommended, it is better to use M
