Andrew Stewart <b...@airbladesoftware.com> wrote: > I was wondering why my Unicorn master process's memory use grows over > time. > > As as I understand it, when I (re)start Unicorn a master process spins > up which loads my Rails app. The master process then brings up worker > processes which handle traffic to the app.
Correct, the master should not grow. If you're using "preload_app true", can you reproduce the growth without it? > As time passes I'm not surprised to see the workers use more memory: > Ruby 1.9's garbage collector doesn't free as much memory as it could and > it's not inconceivable that my code is somewhat relaxed about creating > objects. > > However if the workers are handling the traffic, why does the master > process's footprint grow? Is it simply the inefficient garbage > collector or is there another reason which, hopefully, I could address? If you're using preload_app, I suspect it's some background thread or hook causing it. Otherwise, can you reproduce this with a barebones application? _______________________________________________ Unicorn mailing list - mongrel-unicorn@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
