News for hackers. Stuff that matters.
Re:Heroku's Ugly Secret: The story of how the cloud-king tur... by wwarnerandrew on Wednesday February 13, 2013 @07:06PM (#5216653)
Yes, it's true that the Cedar stack supports forking web servers like unicorn, and that an individual dyno can run multiple workers and therefore serve multiple requests at the same time.

However, dumb routing is still very problematic – even if your dyno can work on two requests simultaneously it's still bad for it to get sent a third request when there are other open dynos.

Also, for apps with a large-ish memory footprint, you can't run very many workers. A heroku dyno has 512mb memory, so if your app has a 250mb footprint, then you can basically only have two workers.

Another essential point to note is that the routing between cedar and bamboo is essentially unchanged. They simply changed the type of apps you can run.

Re:Heroku's Ugly Secret: The story of how the cloud-king tur... by richcollins on Wednesday February 13, 2013 @07:24PM (#5216732)
Right if the apps internal queue is full and it stops accepting connections I'm assuming it will still queue at the dyno level anyway.