lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Terletsky <sx...@yahoo.com>
Subject Re: Retrieval Performance degradation when indexing a numeric field
Date Thu, 04 Apr 2013 05:19:45 GMT
Hi,
We deliberately left the queries the same for both indexes, the one with date field indexed
and the one without. On both indexes the query didn't include the date field, only some string
field.


 
Maxim


________________________________
 From: Itamar Syn-Hershko <itamar@code972.com>
To: user@lucenenet.apache.org 
Sent: Wednesday, April 3, 2013 8:57 PM
Subject: Re: Retrieval Performance degradation when indexing a numeric field
 
What type of queries? This could happen, yes

Try playing with field precision, and moving to filters where possible
On Apr 3, 2013 8:33 PM, "Avi Levy" <levy@wesee.com> wrote:

> Hello,
>
> I have a Lucene.NET index created with version 2.9.4.1. I have re-indexed
> the index from scratch and added a numeric field to the index representing
> a
> date. The field is not stored. The numeric value represents a date in the
> format of yyyyMMddhhmm.
>
> I noticed that when I use queries on the index they take significantly
> longer.
> Below you can see a table for the average query time.
> Each run was of 3000 different queries, all running one after the other
> with
> a short sleep between them.
>
>
>
>
> No dates indexed
>
> Dates indexed
>
>
> Not optimized
>
> 79.76 ms
>
> 312.63
>
>
> Optimized
>
> 75.26 ms
>
> 78.40
>
> I optimized by setting these parameters: UseCompaundFile = false,
> RamBufferSize = 200, TermIndexInterval = 16.
>
> Is this an expected behavior?
> Is there something I can do to improve the performance of non-optimized
> index?
>
>
>
> Thanks,
> Avi
>
>
>
>
>
>
>
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message