3 ms·
It is how Rails server behaves in itself, but that is also how Heroku tells you to do it. Rails can be served with Unicorn ( http://unicorn.bogomips.org/ http:
by kawsper 14y ago
It is how Rails server behaves in itself, but that is also how Heroku tells you to do it.
Rails can be served with Unicorn ( http://unicorn.bogomips.org/ http://unicorn.bogomips.org/ ) which is a forking app-server.
I do believe there was a trick a while back where you could get Heroku to run a Unicorn process on a dyno to get more requests out of it. The process is described here: http://blog.codeship.io/2012/05/06/Unicorn-on-Heroku.html http://blog.codeship.io/2012/05/06/Unicorn-on-Heroku.html
- anon640 14y agoIsn't this kind of a step backwards? Is Rails really that great that people are willing endure these kinds of limitations just to use it?
- kawsper 14y agoRails server is mostly for development mode. When deployed I think most people use either Unicorn, or throw their applications on JRuby that runs on the JVM with some kind of appserver. JRuby have this advantage of being multithreaded, so you can parallelize within a single process, and don't rely on forking. Stock Ruby with MRI have a GIL, and as far as I know only runs on one core. The limitations of stock Ruby is being worked on, but there is still a long way.