lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-11595) optimize SolrIndexSearcher.localCollectionStatistics to use cached MultiFields
Date Tue, 14 Nov 2017 22:08:00 GMT


ASF subversion and git services commented on SOLR-11595:

Commit 0032ce48b3886b226331aec06a5be4dfd4afffb8 in lucene-solr's branch refs/heads/branch_7x
from [~dsmiley]
[;h=0032ce4 ]

SOLR-11595: optimize SolrIndexSearcher.collectionStatistics

(cherry picked from commit 3923e9f)

> optimize SolrIndexSearcher.localCollectionStatistics to use cached MultiFields
> ------------------------------------------------------------------------------
>                 Key: SOLR-11595
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: search
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Minor
>             Fix For: 7.2
>         Attachments: SOLR_11595_optimize_SolrIndexSearcher_collectionStatistics.patch
> {{SolrIndexSearcher.localCollectionStatistics(field)}} simply calls Lucene's {{IndexSearcher.collectionStatistics(field)}}
which in turn calls {{MultiFields.getTerms(reader, field)}}.  Profiling in an app with many
150 fields in the query shows that building the MultiTerms here is expensive.  Fortunately
it turns out that Solr already has a cached instance via {{SlowCompositeReaderWrapper}} (using
MultiFields which has a ConcurrentHashMap to the MultiTerms keyed by field String.
> Perhaps this should be improved on the Lucene side... not sure.  But here on the Solr
side, the solution is straight-forward.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message