From: Michael Fischer <mfischer@zendesk.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Is there a cleaner way of hooking into the event loop?
Date: Tue, 22 Apr 2014 18:30:26 -0700 [thread overview]
Message-ID: <CABHxtY727DZXm3S33E+ygj-0SPe7dhpLRXhh3bZQvs20p=Bh9g@mail.gmail.com> (raw)
In-Reply-To: <CAAtdryNzTzDk+V2bEfePvL6wtxQ3FSW-Nm=EA2eih9RRmZ2cYg@mail.gmail.com>
On Tue, Apr 22, 2014 at 6:21 PM, Sam Saffron <sam.saffron@gmail.com> wrote:
> I am spawning sidekiqs from the master process so I share memory
> better, added this patch
>
> https://github.com/discourse/discourse/commit/4aaedb82d09d53159a99c3c94c0232c3cf5b0725
>
> Thing is I need to be in the master thread for both checks and
> spawning cause of this https://bugs.ruby-lang.org/issues/9751
>
> Is there a cleaner way to hook in?
>From an operational perspective this seems like a significant
premature optimization. I'd think twice before doing it. IME you
really don't want asynchronous job handling in the same process space
as a synchronous preforking webserver. Best to keep your concerns
separated. And RAM is cheap.
--Michael
_______________________________________________
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:[~2014-04-23 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 1:21 Is there a cleaner way of hooking into the event loop? Sam Saffron
2014-04-23 1:30 ` Michael Fischer [this message]
2014-04-23 2:04 ` Sam Saffron
2014-04-23 8:54 ` 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:
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='CABHxtY727DZXm3S33E+ygj-0SPe7dhpLRXhh3bZQvs20p=Bh9g@mail.gmail.com' \
--to=mfischer@zendesk.com \
--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).