TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

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

66 pointsby dschwartz88over 11 years ago

5 comments

oceanplexianover 11 years ago
I'm curious why people put so much effort into scaling Heroku when you could outperform the maximum number of Dynos with only a handful of AWS instances for a fraction the price. It doesn't make sense. We're literally working around a problem that shouldn't exist.
评论 #7105715 未加载
评论 #7105285 未加载
werkshyover 11 years ago
Dynosaur author here, if anyone has questions.
评论 #7103968 未加载
评论 #7102919 未加载
评论 #7102968 未加载
评论 #7105371 未加载
spydertennisover 11 years ago
Doesn't it make more sense to scale based on New Relic response times? Why are you guys using # of users? Depending on the page they are requesting and how the requests are clustered that could produce vastly inferior results.
评论 #7105064 未加载
评论 #7105052 未加载
willcodeforfooover 11 years ago
It's kind of surprising that Heroku hasn't cracked this nut on their own. Perhaps it isn't in their best interest to scale down? Scalability certainly is often touted as one of the benefits of "the cloud".
评论 #7108859 未加载
sergiotapiaover 11 years ago
So I'm curious, how many users per dyno are needed for a typical CRUD rails app?
评论 #7104590 未加载
评论 #7106598 未加载