Hi.
I tried raising the reactor-pool version to 1.0.1 and running tests.
If I do the runWithoutColocation test first and then the runWithColocation test, the runWithoutColocation test measures slower.
So it seems to be an effect of the order of the tests and not an effect of LoopResources.
Luboš Račanský
Thanks for the post. I am trying to understand the situation. My first observation is that in 2025, the current Netty does not accept negative numbers, see github.com/reactor/reactor-netty/blob/main/reactor-netty-core/src/main/java/reactor/netty/resources/LoopResources.java#L136