[
https://issues.apache.org/jira/browse/SOLR-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388910#comment-17388910
]
Mike Drob commented on SOLR-15555:
----------------------------------
[~ben.manes], I'm interested if you have feedback on this use of Caffeine Cache
here -
https://github.com/apache/solr/pull/230/files#diff-99978700f1c69d6a5f6c2190f89c98cfe20c441161db5a183ec002e15cb1be28R841-R850
I still need to set up some JMH profiling here, but I'm not sure if setting a
placeholder like this will be an anti-pattern for Caffeine, given that things
like calculating a doc set or uninverting a field could potentially take a long
time. If it's an approach that makes sense, maybe we consider implementing it
at the cache layer (alternative method signature for opt-in?)
> Use filterCache.computeIfAbsent in SolrIndexSearcher
> ----------------------------------------------------
>
> Key: SOLR-15555
> URL: https://issues.apache.org/jira/browse/SOLR-15555
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mike Drob
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When multiple concurrent queries come in at the same time, in several cases
> they can trigger concurrent computations of a DocSet for the cache. We should
> investigate where this happens and possibly take care to only do a single
> computation when possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
