You actually need to consider your application's memory footprint and web concurrency.
For that kind of scale you will almost certainly want Performance-XL dynos, that's my quick take. To do the math, you need to multiple your web concurrency * your # of dynos, then you have the total number of web servers that can respond to requests. For example, we have web concurrency of 40 on 3 dynos, so we have 120 web servers. With our 120 web servers, I find that we can reasonably accommodate approximately 1000 concurrent users. (So that's about 8-to-1 concurrent users to web servers). But all of this depends on your app's response times too, so it's impossible to say outside of the context of the running app. Since it's very hard to do what you're trying to do, you're better off just installing New Relic and monitoring it as you go, then scaling up. I doubt you will find Heroku to be a bottleneck for you, but you may find that other critical services will bottleneck at that scale (like the database). The best way to do it is to deploy it and monitor it in real time. If you really want benchmarks you can look into a tool like Blaze Meter to flood your servers with fake requests to test the scale. There's really no other way to do it than in real-world conditions. Trying to do the math you're trying to do out of the context of a running app will be sort of futile. -Jason > On Aug 30, 2017, at 6:36 AM, [email protected] wrote: > > [email protected] > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/heroku/topics> > Google Groups > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > > Today's topic summary <> > View all topics > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/heroku/topics> > Heroku Machine Capacity planning for peak load. <x-msg://21/#group_thread_0> > - 2 Updates > <>Heroku Machine Capacity planning for peak load. > <http://groups.google.com/group/heroku/t/2980cd3fb3c98d67?utm_source=digest&utm_medium=email> > > Chaitanya Jadhav <[email protected]>: Aug 29 05:42AM -0700 > > Hello All, > > We have following requirements that we need to handle for the user requests > on our platform. > > 1. dyno-type: web > **Peak Load > - 10,000 concurrent connections ...more > <http://groups.google.com/group/heroku/msg/b39e6e99c8029?utm_source=digest&utm_medium=email> > > Mike Abner <[email protected]>: Aug 29 02:41PM > > What programming language/stack? > > Do you have a budget or is that what you are trying to figure out? > On Tue, Aug 29, 2017 at 5:42 AM Chaitanya Jadhav <[email protected]> > wrote: > > ...more > <http://groups.google.com/group/heroku/msg/11abf1248c2046?utm_source=digest&utm_medium=email> > > Back to top <x-msg://21/#digest_top> > You received this digest because you're subscribed to updates for this group. > You can change your settings on the group membership page > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/heroku/join>. > To unsubscribe from this group and stop receiving emails from it send an > email to [email protected] > <mailto:[email protected]>. ---- Jason Fleetwood-Boldt [email protected] http://www.jasonfleetwoodboldt.com/writing If you'd like to reply by encrypted email you can find my public key on jasonfleetwoodboldt.com <http://jasonfleetwoodboldt.com/> (more about setting GPG: https://gpgtools.org) -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
