From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Forking non web processes
Date: Fri, 25 Oct 2013 20:44:35 +0000 [thread overview]
Message-ID: <20131025204435.GA18120@dcvr.yhbt.net> (raw)
In-Reply-To: <CAAtdryMDGDb6vv0meZxtfGvBfB9P5xm8MqMvwuGQb5HZQF_bdw@mail.gmail.com>
Sam Saffron <sam.saffron@gmail.com> wrote:
> The only reason for this level of crazy is to get the 30% memory
> saving you do when forking off a master in Ruby 2.0s CoW friendly GC.
> I understand this is less traditional, but perfectly acceptable for
> low cost VPS hosting.
>
> The unicorn master does "reap/terminate" the child fork on startup, so
> you are forced to hold off on forking.
You can probably replace a worker process in the after_fork hook
(totally untested)
after_fork do |server, worker|
if worker.nr == 1
server.listeners = [] # drop listen sockets
# keep ticking
Thread.new { worker.tick = Time.now.to_i while sleep(server.timeout/2) }
begin
run_your_own_thing
ensure
exit
end
end
end
Or even just fork off via your Rack app. This will be more portable in
case you want to try a different server. unicorn workers do nothing
special with SIGCHLD, so your app can do whatever it wants with it.
_______________________________________________
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
next prev parent reply other threads:[~2013-10-25 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 20:29 Forking non web processes Sam Saffron
2013-10-25 20:44 ` Eric Wong [this message]
2013-10-25 20:53 ` Sam Saffron
-- strict thread matches above, loose matches on Subject: below --
2013-10-24 11:08 Sam Saffron
2013-10-24 16:17 ` Eric Wong
2013-10-24 16:25 ` Alex Sharp
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=20131025204435.GA18120@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://yhbt.net/unicorn.git/
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).