Rails connection pool size optimizations

Global registration is not a Katello feature, so I don’t see why it’s that obvious.

My bad, I was under the impression sub-man register was performed on the host, but apparently it’s global registration.
Still the test will be a bit different, since without Katello the template will not try content specific commands that can influence the overall performance of the system.

I wonder if moving forward with Saying goodbye to the Katello Event Daemon would also help with this?

It can help, sure. Less threads that we need to hunt for is definitely a good thing to have, although as long as we know exactly how many threads are spawned, it shouldn’t affect us too much.