From: Ben Somers <somers.ben@gmail.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn on shared apps platform
Date: Tue, 26 Feb 2013 08:55:26 -0800 [thread overview]
Message-ID: <CAO1NZArEgdfAdQRXyt9f2YuU8XCazBBZeHQsAY9NpsrtjfrQEg@mail.gmail.com> (raw)
In-Reply-To: <1361894894.97230.YahooMailNeo@web120105.mail.ne1.yahoo.com>
> Can one signal unicorn to increase workers or just spin new set of workers. Any one tried alicorn? https://github.com/bensomers/alicorn.
I'm the author of alicorn; I've tried it :). I only know of one team
that's currently running it in production, but they've been using it
with no difficulties for about six months now. It's meant to solve
exactly the problem you have, dynamically scaling unicorn workers,
though it can't idle an app at zero workers (I think it technically
could; but the results would be bad). Happy to help you with it if
needed.
> Provisioning double memory on deploy can be solved differently by spinning new server that has upgrade and moving load balancer to divert trafic, the netflix way.
I don't like doing that just because of the time it takes to spin up
new servers (even on EC2, it's not instant). If you're running
multiple apps on one box, then you can cheat a little bit, because you
won't need enough memory for running all the apps twice, just enough
to run everything once + one app twice.
-ben
_______________________________________________
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-02-26 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 15:08 Unicorn on shared apps platform Amol Dev
2013-02-26 15:36 ` Hongli Lai
2013-02-26 16:08 ` Amol Dev
2013-02-26 16:55 ` Ben Somers [this message]
2013-02-26 18:15 ` Amol Dev
2013-02-26 17:26 ` Eric Wong
2013-02-26 17:30 ` Hongli Lai
2013-02-26 17:46 ` Eric Wong
2013-02-26 18:18 ` Amol Dev
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=CAO1NZArEgdfAdQRXyt9f2YuU8XCazBBZeHQsAY9NpsrtjfrQEg@mail.gmail.com \
--to=somers.ben@gmail.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).