Ruby MRI when used can at most process a single thread concurrently due to GVL. This results in a over-utilisation if unfavourable distribution of connections is happening.
This tries to prefer less-busy workers (ie. faster to accept
the connection) to improve workers utilisation.
