2 ms·
It was an api endpoint making a number of db and other network requests. The garbage was the accumulation of temporary and response objects that were held for t
by karmakaze 8y ago
It was an api endpoint making a number of db and other network requests. The garbage was the accumulation of temporary and response objects that were held for the long duration of processing, up to half of which could be in the ruby code not waiting on i/o. If the code ran faster there would be more time for gc and handling the incoming request volume.