News for hackers. Stuff that matters.
Re:Heroku XL by sync on Monday February 03, 2014 @10:50AM (#7171205)
Rails servers like Unicorn can still only support ~4 concurrent requests on regular dynos (roughly 1 per virtualized core), lessening the problem but not solving it if you have many requests per second.
Re:Heroku XL by jules on Monday February 03, 2014 @11:26AM (#7171501)
Actually that makes a tremendous difference. It is a bit difficult to explain but even 2 concurrent requests per dyno is a lot better than 1. As you go up from 2 to 3 to 4 the difference quickly becomes minimal. I'll try to explain why, but warning: hand waving ahead!

The problem with only 1 concurrent request is that if that request takes long to process then it can block other requests that are queued up in that dyno. Lets say that 1% of the requests take long. If a dyno can process only 1 request concurrently then at each request there is a 0.01 chance that that will block other requests. If however it can process 4 concurrent requests, then the dyno will only be blocked if it gets 4 long requests at the same time. So there is only a 0.01^4 = 0.00000001 chance that a dyno will be blocked.

Re:Heroku XL by adrianpike on Monday February 03, 2014 @12:47PM (#7172216)
Not quite. If you keep routing to a blocked backend, any requests that hit that backend will have unacceptable latencies. Since the routing is essentially random, you'll still be fielding about 1/4 of your requests to that backend, so one long request winds up making 1/4 of all your requests have unacceptable latencies.
Re:Heroku XL by jules on Monday February 03, 2014 @12:57PM (#7172309)
I don't think that's how it works. Within a single dyno with concurrency of 4 a single request can not block block any requests. It can only block 1 thread, but then the other requests will be processed on the other threads. Routing is only random to dynos, within dynos it is not random.
Re:Heroku XL by oillio on Monday February 03, 2014 @04:02PM (#7173455)
At the end of the day, there must be some applications that cannot be fixed by increasing concurrency to the limit in a standard dyno. They would not bother implementing XL dynos if this was not the case.
Re:Heroku XL by jules on Monday February 03, 2014 @04:32PM (#7173639)
It's most beneficial for application that cannot fit more than 1 on a single dyno.
Re:Heroku XL by thinkbohemian on Monday February 03, 2014 @11:54AM (#7171739)
I run http://codetriage.com/ on Rails 4, Ruby 2.1.0 and have 5 unicorn workers per (regular 1x) dyno. With a little GC tweaking I could likely get 6, but i'm being cautious. With puma hybid server I can get even more concurrency, but don't need it for now.