Neil, A bit of a tangent, but...
I'd imagine varnish may cut down the load on the dynos. Heroku may buy you quick scaling, but it also has other infrastructure (memcached, varnish) in place to alleviate the load. --Keenan On Feb 3, 2011, at 9:17 AM, Christos Zisopoulos wrote: > 100k/minute !!! And I was excited about our 1.4k/minute... > > As far as I can tell: > > Using the UI at api.heroku.com you can get up to 24 dynos. > > Using the CLI, 100. > >> heroku dynos 101 > ! Dynos not allowed > > My guess is your DB will keel over and die way before the dynos run out. And > upgrading the DB is a long winded process: upgrade plan, go into maintenance > mode, make a backup, restore the backup... Hours for our app. > > -christos > > On 3 Feb 2011, at 15:08, Neil Middleton wrote: > >> This week in the UK we had the launch of police.uk, an Django based site >> hosted on EC2. Pretty much straight away it went down through load. From >> talking to the developers, it transpires that they were seeing 100,000+ >> requests per minute, and had to draft in several hundred more EC2 instances >> to cope. >> >> Which leads me to a tasty hypothetical question. If for instance I wanted >> to launch a site like that on Heroku, are there any limits to where you can >> scale too and how long it might take? I know from experience that I can get >> 50 dynos within a couple of seconds, but surely there must be a point where >> this is a little harder to provision? Are there any known limits? What >> happens if I want, say, 5000 dynos right now? At what point does the DB >> layer start to suffer? How would Heroku handle a site of this magnitude >> appearing 'all of a sudden'? >> >> -- >> Neil Middleton >> >> http://about.me/neilmiddleton >> The internet's most comprehensive source for all things Neil Middleton >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To post to this group, send email to heroku@googlegroups.com. >> To unsubscribe from this group, send email to >> heroku+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
