unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Luke Melia <luke@lukemelia.com>
To: mongrel-unicorn@rubyforge.org
Subject: Garbage collection outside of request cycle?
Date: Thu, 6 May 2010 16:29:40 -0400	[thread overview]
Message-ID: <0BFC98E9-072B-47EE-9A70-05478C20141B@lukemelia.com> (raw)

I've been analyzing our Unicorn-powered Rails app's performance, and have found that garbage collection is a big factor in slow requests.

In the interest of avoiding those performance hits while handling requests, would it be possible to have a unicorn worker run garbage collection after handling a request and before waiting for the next one? Would this be a good idea?

Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

             reply	other threads:[~2010-05-06 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 20:29 Luke Melia [this message]
2010-05-06 20:57 ` Garbage collection outside of request cycle? Eric Wong
2010-05-06 21:12   ` Eric Wong
2010-05-06 23:17   ` Luke Melia
2010-05-13 20:29     ` Luke Melia
2010-05-14 19:02       ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0BFC98E9-072B-47EE-9A70-05478C20141B@lukemelia.com \
    --to=luke@lukemelia.com \
    --cc=mongrel-unicorn@rubyforge.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).