[
https://issues.apache.org/jira/browse/SOLR-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631638#comment-17631638
]
Jason Gerlowski commented on SOLR-16531:
----------------------------------------
I appreciate the extra explanation, but I feel like you're arguing against a
point that no one's putting forward here. We all agree this is important. We
all agree this is worth looking into. And I've said at least twice now that I
plan to take a look personally. I don't think that's "dismissive" by any
stretch.
No one's questioning whether this should get fixed: everyone's in agreement on
that already.
The open question is whether it should be a blocker. And looking at the
question with my "Apache Hat" on, I just don't see much case there. We'd (in
theory) make tens of thousands of users the world over wait - not on a security
fix, not on a stability issue, not even on a performance problem that's likely
to impact them - but on a 7% slowdown of a less-common operation that impacts
two companies *in the world*?
I value those companies and their role in our community. And - as you alluded
to - I even work at one of them! So I'm the furthest thing from dismissive
here, believe me. But we have a responsibility to make community decisions
with the whole community in mind.
bq. So, they just refuse to upgrade to a newer version of Solr and they just
keep patching their existing fork.
I'd hate to think that this ticket would cause companies to fork, or invest
more in their forks. But "No Blocker Tag = More Forks and Fewer Devs" seems
like a false choice to me. There are plenty of paths to getting this in 9.2
that don't involve "priority:Blocker".
> Performance degradation due to introduction of JAX-RS
> -----------------------------------------------------
>
> Key: SOLR-16531
> URL: https://issues.apache.org/jira/browse/SOLR-16531
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: 9.2
>
> Attachments: Screenshot from 2022-11-09 11-20-44.png,
> results-with-patch.tar.gz
>
>
> During performance benchmarking on branch_9x, I observed a slowdown in
> restart performance since commits in SOLR-16347. See attached screenshot.
> CC [~gerlowskija].
> http://mostly.cool/cluster-test-with-patch.html
> The benchmark is here:
> https://github.com/fullstorydev/solr-bench/blob/ishan/repeatable-jenkins/suites/cluster-test.json.
> This suite was run after retro-actively applying the parallelStream patch
> from SOLR-16414:
> https://github.com/apache/solr/commit/b33161d0cdd976fc0c3dc78c4afafceb4db671cf.diff
>
> Effort to automate these benchmarks is WIP and tracked here: SOLR-16525.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
