Show HN: Dynosaur, An autoscaler for Heroku using Google Analytics Live

Re:Show HN: Dynosaur, An autoscaler for Heroku using Google ... by sergiotapia on Wednesday January 22, 2014 @01:41PM (#7104487)

So I'm curious, how many users per dyno are needed for a typical CRUD rails app?

[ Parent | on HN ]

Re:Show HN: Dynosaur, An autoscaler for Heroku using Google ... by werkshy on Wednesday January 22, 2014 @02:00PM (#7104590)

That really depends on your app and your caching strategy. If you are doing something complex or memory intensive (or your app is poorly optimized), or if your users are highly engaged, it could be in the low tens of users! If you are doing a lot of caching you should be able to serve static pages on the order of several hundred or more per dyno.

[ Parent | on HN ]

Re:Show HN: Dynosaur, An autoscaler for Heroku using Google ... by hayksaakian on Wednesday January 22, 2014 @08:53PM (#7106598)

You can get a lot out of 1 dyno.

On two dynos you can have 1 do background jobs and 1 server content

obviously it varies, but you don't inherently need many.

[ Parent | on HN ]