On Jan 9, 2006, at 8:41 PM, Rick Olson wrote:
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.
I deploy apps on a shared hosting server without the spinner, and
everything is fine. I just use the facilities provided by Lighttpd.
Note, too, that boot.rb is not the "whole Rails environment"--that's
environment.rb. Boot.rb just sets up the initializer so that the path
to the railties can be found. Thus, spinner/spawner/etc. load only a
bare minimal subset of the rails environment, just enough to find the
files they need in railties/lib/commands/process.
- Jamis
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
