News for hackers. Stuff that matters.
Re:An expensive line of code: scaling Node.js on Heroku (2013) by brendangregg on Thursday September 29, 2016 @12:14AM (#12603251)
"And then it hit me"... ok, a great story, but you have to wonder what people would do if they didn't just guess the answer.

That much slowness may be disk I/O bound, which would show up in the USE method, or even just my Linux performance checklist[1]. It'd also show up by tracing blocking events, even an off-CPU flame graph, but that's overkill.

[1] http://techblog.netflix.com/2015/11/linux-performance-analys...

Re:An expensive line of code: scaling Node.js on Heroku (2013) by tayo42 on Thursday September 29, 2016 @12:25AM (#12603296)
This is on heroku though. You cant really do any of that?
Re:An expensive line of code: scaling Node.js on Heroku (2013) by brendangregg on Thursday September 29, 2016 @04:26PM (#12608486)
Ah, you may be right! I have not used heroku. I'd hope they'd make some of the metrics available somewhere.