Ben Somers <somers....@gmail.com> wrote: > First: auto-killing bloated workers. My current app has some memory > leakage that wasn't really visible on our older passenger setup, since
Btw, you reported issues with memory usage on a Ubuntu system a few months ago, is this the same system? Are you using stock malloc() or tcmalloc()? (tcmalloc comes standard with REE afaik and never releases memory to the kernel). For glibc malloc (ptmalloc) users I mentioned MALLOC_MMAP_THRESHOLD_, but forgot about MALLOC_ARENA_MAX. Since MRI is mostly single-threaded (especially the memory allocation portions), I'm tending to think the per-thread optimizations in glibc malloc do not help in most cases and will only lead to internal fragmentation. So perhaps setting MALLOC_ARENA_MAX=1 (perhaps along with mmap threshold) in the environment will reduce fragmentation and memory usage. It doesn't look like the MALLOC_ARENA_* environment variables are in the manpages, yet: http://udrepper.livejournal.com/20948.html _______________________________________________ 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
