Jul 2011 22:42:44 +0200
> Von: Simon Willnauer
> An: java-user@lucene.apache.org
> Betreff: Re: AutomatonQuery Caching
> Hi rene,
>
> On Tue, Jul 12, 2011 at 10:12 PM, Rene Hackl-Sommer
> wrote:
> > This sounds plausible, even if manually cleaning the Java cache has no
Hi rene,
On Tue, Jul 12, 2011 at 10:12 PM, Rene Hackl-Sommer wrote:
> This sounds plausible, even if manually cleaning the Java cache has no
> effect. Probably a JDK/JRE mismatch somewhere, just have to find the spot.
this is very likely your OS pushing frequently use data into RAM via
FS cache.
This sounds plausible, even if manually cleaning the Java cache has no
effect. Probably a JDK/JRE mismatch somewhere, just have to find the spot.
Thanks,
Rene
Am 12.07.2011 19:22, schrieb Robert Muir:
On Tue, Jul 12, 2011 at 10:42 AM, "René Hackl" wrote:
Hi,
I am running some AutomatonQueri
On Tue, Jul 12, 2011 at 10:42 AM, "René Hackl" wrote:
> Hi,
>
> I am running some AutomatonQueries and see caching effects happening, that I
> can't seem to get rid of. E.g. an AutomatonQuery takes
>
> Run 1: 3000 ms
> Run 2 and all subsequent runs: 250 ms
>
> The IndexSearcher is closed after ev
Hi,
I am running some AutomatonQueries and see caching effects happening, that I
can't seem to get rid of. E.g. an AutomatonQuery takes
Run 1: 3000 ms
Run 2 and all subsequent runs: 250 ms
The IndexSearcher is closed after every full query circle (and opened via
open(Directory), so the Index
