[
https://issues.apache.org/jira/browse/SOLR-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18110368#comment-18110368
]
Renato Haeberli commented on SOLR-17841:
----------------------------------------
[~dsmiley] [~arupchauhan] For multi-threaded test you can have different
outcomes depending on the chip architecture underneath, you can have a test
failing outright on ARM, but working fine on x86. As far as I understand this
is due to the stricter memory model on x86, which is more forgiving if e.g.
when a needed volatile is missing.
> Investigate multithreaded search performance bottlenecks
> --------------------------------------------------------
>
> Key: SOLR-17841
> URL: https://issues.apache.org/jira/browse/SOLR-17841
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 10.0
>
> Attachments: image-2026-08-26-15-39-44-012.png, profile.html
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Ever since multithreaded search (SOLR-13350) was introduced, there has been
> not much effort to benchmark the performance benefit or investigate the
> performance bottlenecks. Anecdotally, it is not faster than single threaded
> execution.
> Thanks to [~kevinliang01] [~liangkaiwen] [~liangkw16] and [~dsmiley] for
> bringing this up, yesterday on a dense vector working group meeting.
> I'm marking this as a release 10.0 blocker, because it is embarrassing to be
> releasing with such a gaping hole.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
