[jira] [Commented] (LUCENE-6233) CheckIndex is dog slow when checking term vectors

["Michael McCandless (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-6233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314391#comment-14314391 ] 

Michael McCandless commented on LUCENE-6233:
--------------------------------------------

This was introduced with LUCENE-5610

I'll fix the nightly Lucene benchmark to plot CheckIndex time ... we could have spotted this performance regression.

> CheckIndex is dog slow when checking term vectors
> -------------------------------------------------
>
>                 Key: LUCENE-6233
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6233
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>
> I'm working on a test that creates a biggish index and I noticed the CheckIndex takes a surprisingly long time to check term vectors.
> I profiled it and uncovered that we spend a lot of time (not sure this explains all of it) in Terms.getMin/getMax.  Since CompressingTermVectorsReader doesn't impl these methods efficiently (which is fine), we fallback to super's impl, which does a digit-by-digit binary search using seekCeil.
> But for TVs this sometimes results in a linear scan.
> I think CheckIndex should not check Terms.getMin/Max for TVs?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org