[jira] [Commented] (SOLR-16531) Performance degradation due to introduction of JAX-RS

["Ishan Chattopadhyaya (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653826#comment-17653826 ] 

Ishan Chattopadhyaya commented on SOLR-16531:
---------------------------------------------

bq. On a maybe related note, there seems to be a bug in the ishan/repeatable-jenkins solr-bench branch that I was pointed to in a comment pretty early-on in this thread. See here for the details, but the gist: the start-time calculation on "repeatable-jenkins" accidentally subtracts the recovery time instead of adding it (at least, as of 1d1a36). I mentioned this in a fullstorydev/solr-bench issue here and asked for some clarification on how (or whether) to submit a fix. Take a look when you get a chance please!

I'll take a look.

bq. Additionally, on runs that create a large number of collections (i.e. sporadically with 700 but frequently with 800 or more colls) the "clusterstatus" task runs into problems creating these collections. The CREATE request times out and the Solr logs have a suspicious loooking error message about an expected overseer node being missing. Running with the full 1000 collections that Ishan and Noble's numbers were based on, it takes me somewhere between 5 and 10 benchmark attempts to get a clean, usable run. Again, maybe this is something specific to running "locally"? Curious if any of this rings a bell for anyone more familiar with running this suite, maybe Ishan can chime in.

Looks like this could be an issue with hardware? Can you please post the specs of the machine where this was running?

bq. I'm optimistic that the improvements to our Jersey-integration take a good bite out of the perf degradation. But whatever the solr-bench results from others might show, I expect we probably still aren't quite "there" yet and more improvement will be needed. So let's talk next steps.

Sounds good. Please let me know if you have a branch with the improvements ready that you want me to test (solr-bench) on the same hardware where I've been running the tests till now.

bq. but haven't been able to reproduce anything in the "33%" ballpark that Ishan mentioned a few comments up

Just to cross check, I think I should re-run the benchmark once again and see how it goes.

> 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-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org