lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2939) Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when adding a new field to MemoryIndex
Date Sun, 27 Feb 2011 05:17:58 GMT

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

Mark Miller commented on LUCENE-2939:
-------------------------------------

Fair enough (this setting is well before my time AFAIK) - but not my intent with this issue
- which is just to fix this little perf bug.

> Highlighter should try and use maxDocCharsToAnalyze in WeightedSpanTermExtractor when
adding a new field to MemoryIndex
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2939
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2939
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: contrib/highlighter
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>         Attachments: LUCENE-2939.patch
>
>
> huge documents can be drastically slower than need be because the entire field is added
to the memory index
> this cost can be greatly reduced in many cases if we try and respect maxDocCharsToAnalyze
> the cost is still not fantastic, but is at least improved in many situations and can
be influenced with this change

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message