Jetty with security manager enabled does a reverse lookup on the ip.
Depending on settings, that can slow things down. In my case, it caused
timeouts.
https://lists.apache.org/thread/po5qwkgpt3qf0qfv4p8rrqj3blm2wcpz
-Tim
On Fri, May 24, 2024 at 2:26 PM Eric Pugh
wrote:
> I’d be curious if oth
It might also be http2. Ive seen numerous issues with http2 performance
(which will hopefully be fixed soon). This can be tested with
“-Dsolr.http1=true”
- Houston
On Fri, May 24, 2024 at 1:25 PM Eric Pugh
wrote:
> I’d be curious if other folks have seen this either anecdotally or even
> better
I’d be curious if other folks have seen this either anecdotally or even better
through some performance testing!
> On May 24, 2024, at 9:12 AM, Tim Funk wrote:
>
> solr9 turns security on manager by default. This has a high probability of
> a performance impact..
>
> disable via adding to star
solr9 turns security on manager by default. This has a high probability of
a performance impact..
disable via adding to startup
export SOLR_SECURITY_MANAGER_ENABLED=false
-Tim
On Thu, May 23, 2024 at 11:23 AM elisabeth benoit
wrote:
> Hello,
>
> We've just migrated one of our services from sol
Thanks a lot for your answer.
Will check that out.
Le jeu. 23 mai 2024 à 20:46, Oleksandr Tkachuk a
écrit :
> Check your clocksource
> cat /sys/devices/system/clocksource/clocksource0/current_clocksource
>
> Also check your other hardware characteristics, like cpu freq and governor,
> ram speed
Check your clocksource
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
Also check your other hardware characteristics, like cpu freq and governor,
ram speed, drive performance/schedulers. Perhaps additional checks like cpu
bench, fio will not hurt.
Also disable java security m
