Re:Ruby has been fast enough for 13 years
by chrisseaton on Monday May 16, 2016 @06:10PM
(#11710042)
But the graph shows time in waiting on web requests (dark green), time waiting on cache (teal), time waiting on the database (brown) and time queued before the interpreter gets the request (light green) separately to time spent running the Ruby interpreter. It's a cumulative graph.
So if the IO isn't web requests, cache, database or waiting in a queue, what can the interpreter be waiting on? Local files?
From the article the slowness is when "a dyno is tied up due to a long-running request" -- so, we they are probably still talking about slow IO operations, and servers running on the dyno that are not async to free it up in between.
From Heroku's one optimization page: "Most applications are not CPU-bound on the web server".
https://devcenter.heroku.com/articles/optimizing-dyno-usage
(And Heroku might be an outlier in having high real-cpu use too, as they tend to over-provision).