3 ms·Nope it was Ruby / Rails itself.by ksec 8y agoNope it was Ruby / Rails itself.aantix 8y agoWas it an issue with Passenger and the number of concurrent connections it could hold?