[katello-devel] Fedora 18 state

[Bryan Kearney]

On 02/22/2013 08:39 AM, Lukas Zapletal wrote:
> After studying possible deployment solutions for Ruby, I am not under
> impression mod_passenger is the best technology out there and I am
> afraid we will avoid this the that, but we can expect other issues.
>
> I would like to talk about this more, maybe after my presentation next
> deep dive. I wonder how will this scale up, because passenger is
> strictly forking only solution and katello boot time is about 15
> seconds. It can work well with REE/Rubinius patched Rubies with better
> forking memory management, but I wonder what this will do with MRI Ruby
> and Katello.
>
> My major concern is this is out of the frying pan into the fire. I'd
> rather postpone mod_passenger talk a little bit more.
>
> Isn't there really a workaround?


I thought that mod passenger was the defacto rails deployment model 
right now? Is each request a new process? I thought there was pooling 
going on.

-- bk