Results 1 to 2 of 2
  1. #1
    tinwelint is offline Member
    Join Date
    Jan 2012
    Posts
    2
    Rep Power
    0

    Default Numeric range query way slower (3.5 vs 3.1)

    Hi,

    I'm trying to upgrade from Lucene (java) version 3.1 to 3.5 and see a performance drop in 3.5 compared to 3.1 (3x faster in 3.1) when doing numeric range queries. Profiling shows that an enormous amount of BooleanScorer$Bucket objects are created in 3.5 and none in 3.1.

    Am I the only one observing this or is it a general issue. Is there any workaround for the performance issue?

    Best,
    Mattias

  2. #2
    tinwelint is offline Member
    Join Date
    Jan 2012
    Posts
    2
    Rep Power
    0

    Default Re: Numeric range query way slower (3.5 vs 3.1)

    It's mostly in unsorted range queries... for sorted range queries 3.5 seems to be just a tad slower than 3.1. I found this in 3.5 (BooleanScorer.java:160-162)

    for(int idx=0;idx<SIZE;idx++) {
    buckets[idx] = new Bucket();
    }

    eager initialization of (1 << 11 = 2048) Bucket objects for each BooleanScorer, and that's what seems to kill the performance.

Similar Threads

  1. Range Query Issue
    By euphreme in forum Lucene
    Replies: 0
    Last Post: 10-20-2011, 11:57 PM
  2. Replies: 8
    Last Post: 03-12-2010, 05:30 PM
  3. Replies: 1
    Last Post: 07-14-2009, 08:04 PM
  4. JXL, Numeric data issue
    By only2008 in forum Java Servlet
    Replies: 0
    Last Post: 02-27-2009, 12:36 PM
  5. get numeric value from a text field
    By Lehane_9 in forum New To Java
    Replies: 2
    Last Post: 06-14-2008, 04:19 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •