Where are my manners :-/
Anyway, I found the answer to my own request.
http://www.cnlp.org/apachecon2005/
Looks like some cool work, I only wish I could hear the accompanying speech.
Cheers,
-Luke
On 12/11/05, gekkokid <[EMAIL PROTECTED]> wrote:
>
> please :)
> - Original Message -
> From:
On Wednesday 07 December 2005 10:51, Andrzej Bialecki wrote:
> Paul Elschot wrote:
> >On Saturday 03 December 2005 14:09, Andrzej Bialecki wrote:
> >>Paul Elschot wrote:
> >>
...
> >>>This is one of the cases in which BooleanScorer2 can be faster
> >>>than the 1.4 BooleanScorer because the 1.4 Boo
please :)
- Original Message -
From: "Luke Nezda" <[EMAIL PROTECTED]>
To:
Sent: Sunday, December 11, 2005 6:28 PM
Subject: Re: ApacheCon next week
Hello Grant-
Could you post the material you present (eg slides, handouts, etc) for those
of us who cannot attend?
Thanks in advance,
-Luk
Hello Grant-
Could you post the material you present (eg slides, handouts, etc) for those
of us who cannot attend?
Thanks in advance,
-Luke
On 12/9/05, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
>
> Any one planning on going to ApacheCon next week? I will be giving a
> talk on Lucene on Monday af
I can't think of a good reason for you to keep the index in memory - The
performance increase (from blazing-fast to super-blazing-fast) just isn't
something your users are going to notice. And it's at the cost of building
the index from scratch every time you start up.
Eventually, for one reason
You also might try -Xbatch or -Xcomp to see if that fixes it (or
reproduces it faster).
Here's a great list of JVM options:
http://blogs.sun.com/roller/resources/watt/jvm-options-list.html
-Yonik
On 12/11/05, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> Sounds like it's a hotspot bug.
> AFAIK, hots
Sounds like it's a hotspot bug.
AFAIK, hotspot doesn't just compile a method once... it can do
optimization over time.
To work around it, have you tried pre previous version: 1.5_05?
It's possible it's a fairly new bug. We've been running with that
version and Lucene 1.4.3 without problems (on Op
On a related topic: yesterday I posted a round-up of all the possible
filtering options in Lucene with timings and example code to the WIKI :
http://wiki.apache.org/jakarta-lucene/FilteringOptions
One of the options demonstrated is along the lines of Chris's suggestion.
Cheers,
Mark
First, thank you Chris, Yonik, and Dan for your ideas as to what might be
causing this problem.
I tried moving things around so that the IndexReader is still open when it
calls TermFreqVector.getTerms()/TermFreqVector.getTermFrequencies(). It
didn't seem to make any difference.
I also tried
