2006 3:14:20 PM
Subject: Refactored FuzzyTermEnum
I refactored the org.apache.lucene.search.FuzzyTermEnum
edit distance implementation. It now only uses a single
pair of arrays, and those never get resized. That required
turning the order of text/target around in the loops. You'll
see th
I'm still waiting for my employer to send in the CCLA. :(
But I've got a cool name for this thing - "lube" - contrib/lube.
Otis
- Original Message
From: Marvin Humphrey <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Wednesday, June 14, 2006 3:51:52
On Thu, 2006-06-15 at 11:42 +0200, karl wettin wrote:
>
> 2. Standard RAMDirectory:
Oups, I got the headers wrong here. Again:
With your fixes:
1000 fuzzy~0.1, 121 per min.
1000 fuzzy~0.2, 190 per min.
1000 fuzzy~0.3, 342 per min.
1000 fuzzy~0.4, 456 per min.
1000 fuzzy~0.5, 578 per min.
1000 f
On Tue, 2006-06-13 at 15:14 -0400, Bob Carpenter wrote:
> I refactored the org.apache.lucene.search.FuzzyTermEnum
Nice!
> Does anyone have regression/performance test harnesses?
I have a quite unscientific test I ran. 500 documents in corpus. One
index reader. A new Index searcher for each query
On Jun 13, 2006, at 12:14 PM, Bob Carpenter wrote:
Does anyone have regression/performance test harnesses?
There's been talk of formalizing a benchmarker suite. Andrzej wrote
something a while ago; I don't know if it would be appropriate for this.
The benchmarker I wrote is indexing only
: I don't know what the protocol is for one-off contributions.
I'm not sure what you mean by a "one-off contribution" but the process for
submiting changes/improvements/additions was recenlty wiki-ized...
http://wiki.apache.org/jakarta-lucene/HowToContribute
(Incidently, please feel free to sha
I refactored the org.apache.lucene.search.FuzzyTermEnum
edit distance implementation. It now only uses a single
pair of arrays, and those never get resized. That required
turning the order of text/target around in the loops. You'll
see that with the pair of arrays method, they get re-used
hand
