I'm not seeing any anomalies with the request pool patch in production, so it's now merged in master. I've also added instrumentation code so you could theoretically add a file like config/initializers/instrumentation.rb and subscribe to the 'with.request_pool' event to either feed it into the logger or your custom monitoring system to observe hits/misses and durations #mastodev
By "hit" I mean when an already established connection could be re-used, and "miss" when a new connection had to be established
so in an ideal network scenario,
Hit or miss?
I guess they never miss, huh?
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!