* Hello excellent friends
@ 2010-08-31 3:57 Curtis
2010-08-31 6:17 ` Eric Wong
0 siblings, 1 reply; 2+ messages in thread
From: Curtis @ 2010-08-31 3:57 UTC (permalink / raw)
To: mongrel-unicorn
I have read your tun in article and I have tried to make sysctl changes - the benchmarks are not very significant. I love how well the signals are laid out and how excellently unicorn responds to them - I am hoping to get back to mongrel like performance . We were using nginx to haproxy to 32 mongrels
No I have set up a unix domain socket with 2mb send and receive buffer and a backlog of 2048 - I didn't see a change with the send receive buffer tuning and I have yet to try a smaller backlog to see. If that helps. Any info?
I am tuning for osx in dev and centos5 in production. Thank you for your great work cleaning mongrel into a first class unix friend.
--
_______________________________________________
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Hello excellent friends
2010-08-31 3:57 Hello excellent friends Curtis
@ 2010-08-31 6:17 ` Eric Wong
0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2010-08-31 6:17 UTC (permalink / raw)
To: unicorn list
Curtis <curtis.schofield@gmail.com> wrote:
> I have read your tun in article and I have tried to make sysctl
> changes - the benchmarks are not very significant. I love how well the
> signals are laid out and how excellently unicorn responds to them - I
> am hoping to get back to mongrel like performance . We were using
> nginx to haproxy to 32 mongrels
>
> No I have set up a unix domain socket with 2mb send and receive buffer
> and a backlog of 2048 - I didn't see a change with the send receive
> buffer tuning and I have yet to try a smaller backlog to see. If that
> helps. Any info?
Hi, I'm not sure what size of requests and responses you get, but 2mb
seems like a lot, especially for requests (unless you handle a lot of
big uploads).
Even with large requests/responses, huge buffers means more pressure on
the kernel allocator and you're also hurting CPU cache locality. So
larger buffers can hurt performance as well as help, I'll make a note of
that in the documentation.
The backlog shouldn't change performance much. A larger one can let you
withstand short traffic bursts and increase reliability while
benchmarking.
> I am tuning for osx in dev and centos5 in production. Thank you for
> your great work cleaning mongrel into a first class unix friend.
You're welcome!
--
Eric Wong
_______________________________________________
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-08-31 6:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-08-31 3:57 Hello excellent friends Curtis
2010-08-31 6:17 ` Eric Wong
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).