> > I'm not sure I understand the question. You can start FCGIs any way
> > you want. The spawner is just a shortcut for starting many FCGIs at
> > once and the spinner is a insurance against fallen FCGIs. How does
> > either have any effect on RAM or start-up time?
>
> The spinner process is running all the time, and because it has loaded
> and initialized the whole Rails environment (boot.rb etc.) it uses a lot
> of RAM. The same goes for the spawner process. It is started every
> #{interval} seconds, and because it loads the Rails environment every
> time - this can put a considerable load on a small server. IMO neither
> spinner nor spawner do really need the Rails environment, all they do is
> to call external scripts.If you're in an environment where the RAM usage of 1 spinner is a concern, then you probably don't need/want the functionality of the spinner anyway. The spawner is triggered by the spinner, so if you just use it on its own, then it only uses the RAM for a few seconds until all the spinners are started. But hey, if you can make a silky clean refactoring that makes the scripts not require the environment startup, but still use stubs like all the others, then I'm all game for applying! -- David Heinemeier Hansson http://www.loudthinking.com -- Broadcasting Brain http://www.basecamphq.com -- Online project management http://www.backpackit.com -- Personal information manager http://www.rubyonrails.com -- Web-application framework _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
