问题
I wonder, in general is it more like PHP (it loads into memory, executes, and dies for each connect). Or it like Node.js (single instance stays in memory and accepts all requests)
回答1:
Technically it's the latter, but depending on the application server, it can be made to look like the former because the former is easier to manage. One example is Phusion Passenger. Take a look at https://www.phusionpassenger.com/ and http://www.modrails.com/documentation/Architectural%20overview.html
回答2:
Second option.
In fact it Ruby that boot the application (can have multiple instances depending of the case .i.e: using puma you can request multiple workers to handle requests) then as soon as ready (depending of the side of your application .i.e: if your routes.rb file where you build each URLs is huge, it will take more time of course) the application start to handle the requests.
来源：https://stackoverflow.com/questions/17706827/how-rails-server-on-production-works