[
https://issues.apache.org/jira/browse/SOLR-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417774#comment-17417774
]
Mark Robert Miller commented on SOLR-15555:
-------------------------------------------
I saw a small hit in before and after testing, but nothing that was really
unexpected. The cost of calculation in that benchmark is tiny and all costs are
essentially very low, so that async option adds measurable coordination costs
vs every thread just ramming through on its own. But the more normal and common
case would be less cache value calculation cost and resource usage which that
benchmark is not geared towards.
> 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
> Assignee: Mike Drob
> Priority: Major
> Fix For: main (9.0), 8.10
>
> Attachments: OUTPUT-org.apache.solr.search.TestRangeQuery.txt.gz,
> SOLR-15555.test-fix.patch
>
> Time Spent: 5.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]
