News for hackers. Stuff that matters.

A comment on I left Heroku for OpsWorks and shaved 40% off response times. Parent comment

Re:I left Heroku for OpsWorks and shaved 40% off response times by swrobel on Friday February 07, 2014 @04:45PM (#7198950)
Agree with most of what you say, but adding dynos increases concurrency but doesn't do anything to reduce response times. Sometimes you just need a faster box.
[ Parent | on HN ]
Re:I left Heroku for OpsWorks and shaved 40% off response times by thinkbohemian on Friday February 07, 2014 @05:48PM (#7199300)
Or a bigger (more RAM) box, I posted this to the Ruby Rouges mailing list on tail latencies: https://gist.github.com/schneems/8849116

Concurrency is only half the battle with tail latencies. Of course dedicated CPU helps as well :)

[ Parent | on HN ]
Re:I left Heroku for OpsWorks and shaved 40% off response times by swrobel on Friday February 07, 2014 @06:13PM (#7199409)
Good stuff schneems, in my case, too little, too late.
[ Parent | on HN ]
Re:I left Heroku for OpsWorks and shaved 40% off response times by thinkbohemian on Friday February 07, 2014 @06:41PM (#7199531)
Understood, can't be everything to every one. BTW thanks for sticking around and answering questions/engaging :)
[ Parent | on HN ]
Re:I left Heroku for OpsWorks and shaved 40% off response times by swrobel on Friday February 07, 2014 @07:36PM (#7199765)
gladly :)
[ Parent | on HN ]