Thanks darragh. This looks like search API performance issue as noted above, I will dig in to HAR file and get back.

Yeah, this is strange for sure from an SSE configure pov because the cost of what it is doing should be constant and small i.e. it is not searching anything or moving data around.

I will look into this too from an SSE pov, but one thing I plan for this is to make the configure process completely async + remove all locking on the request path. Of course that will only have a limited effect if it's a case that the host is starved of threads from the request thread pool because of other long-running requests.

tfennelly this starvation of things may be what has been seen elsewhere (with github oauth in some cases?).

Also - can I ask a dumb question - what is a "HAR" ?

A har file is a file you can generate from the network log panel in the dev tools in the browser.

tfennelly you can upload the HAR to https://toolbox.googleapps.com/apps/har_analyzer/ and view the captured data and requests that occurred within the browser session.

Relates to search API performance issue.

Search API performance issue

Closing this issue. We have identified issues and opened tickets for relevant performance improvements in specific components: JENKINS-38251, JENKINS-38252, JENKINS-38253 and JENKINS-38087.

Thanks for filing this Andreas - fixing the performance issues above is a top priority for our team

see also: https://issues.jenkins-ci.org/browse/JENKINS-38335