---
title: "Comment by Min.K (Minkiu) Kim on \"Java's reactive connection pooling performance caveat\" | Hashnode"
description: "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 ru"
url: "https://hashnode.com/posts/javas-reactive-connection-pooling-performance-caveat/64a1d8e1e16902f78ec7f9a6/comment/64f1517e052b196d0934cc4d"
---

[Discussion](https://hashnode.com/posts/javas-reactive-connection-pooling-performance-caveat/64a1d8e1e16902f78ec7f9a6)

Comment [Java's reactive connection pooling performance caveat](https://hashnode.com/posts/javas-reactive-connection-pooling-performance-caveat/64a1d8e1e16902f78ec7f9a6)

[Min.K (Minkiu) Kim](https://hashnode.com/@mink)

[Sep 1, 2023](https://hashnode.com/posts/javas-reactive-connection-pooling-performance-caveat/64a1d8e1e16902f78ec7f9a6/comment/64f1517e052b196d0934cc4d)

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.

[Piotr](https://hashnode.com/@PiDu)

[Sep 1, 2023](https://hashnode.com/posts/javas-reactive-connection-pooling-performance-caveat/64a1d8e1e16902f78ec7f9a6/comment/64f1517e052b196d0934cc4d#reply-64f1ee1b94e5c8763b3f70a4)

Hey, maybe I have not mentioned it but the tests were meant to be launched separately. I did not take much effort to properly isolate them. I guess when you launch them separately the results are reproducible right?
