rtn.entrySet();
}
}
final SoftLinkMap readerCache=new SoftLinkMap();
//final Map> readerCache = new
WeakHashMap>();
_
yannianmu(母延年)
From: Robert Muir <mailto:rcm...@gmail.com>
Date: 2015-01-30 12:03
To: dev@lucene.apache.org
Subject: Re: Our Opt
>
> Uwe
>
>
>
> -
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: u...@thetaphi.de
>
>
>
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Friday, January 30, 2015 5:04 AM
> To: dev@lu
-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http://www.thetaphi.de
eMail: u...@thetaphi.de
From: Robert Muir [mailto:rcm...@gmail.com]
Sent: Friday, January 30, 2015 5:04 AM
To: dev@lucene.apache.org
Subject: Re: Our Optimize Suggestions on lucene 3.5
I am not sure this is th
final Map> readerCache = new
WeakHashMap>();
yannianmu(母延年)
From: Robert Muir<mailto:rcm...@gmail.com>
Date: 2015-01-30 12:03
To: dev@lucene.apache.org<mailto:dev@lucene.apache.org>
Subject: Re: Our Optimize Suggestions on lucene 3.5
I am not sure this is the case.
I am not sure this is the case. Actually, FieldCacheImpl still works as
before and has a weak hashmap still.
However, i think the weak map is unnecessary. reader close listeners
already ensure purging from the map, so I don't think the weak map serves
any purpose today. The only possible advantage
Hi,
parts of your suggestions are already done in Lucene 4+. For one part I can
tell you:
weakhashmap,hashmap , synchronized problem
1. FieldCacheImpl use weakhashmap to manage field value cache,it has memory
leak BUG.
2. sorlInputDocunent use a lot of hashmap,linkhashmap for field,that wea
