Best practice about max_pool_size vs cores

27 views
Skip to first unread message

Mathieu Martin

unread,
Feb 18, 2013, 2:23:13 PM2/18/13
to phusion-...@googlegroups.com
Hi!

I'm setting up 2 servers with Passenger, serving a single web application.

The documentation suggests at least the same amount of passenger instances as available cores, to increase concurrency. I agree that this is the bare minimum you can do to get good concurrency.

Memory consumption is not really an issue for us. Our servers are trivial to scale up memory-wise.

So I'm wondering, if memory is not an issue, is there a higher baseline I can use for my max pool size? Would cores x 2 still increase concurrency (even if not linearly), or am I already in the zone where I'll be context-switching too much?

Thanks a lot,

Mat

Hongli Lai

unread,
Mar 11, 2013, 10:07:21 AM3/11/13
to phusion-...@googlegroups.com
We're going to publish an article about this tomorrow. Please keep an
eye on the Phusion blog.
--
Phusion | Ruby & Rails deployment, scaling and tuning solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)
Reply all
Reply to author
Forward
0 new messages