On Tue, Oct 22, 2013 at 12:18 PM, John R Pierce <pierce@hogranch.com> wrote:
On 10/22/2013 11:25 AM, andy wrote:
Hum.. I had not thought of that. My current setup uses 40 max connections, and I don't think I've ever hit it. I use apache and php, and my db connections are not persistent.
that style of php programming, you're getting some HUGE overhead in connect/disconnect per web page. putting pg_bouncer in the middle will make a HUGE improvement, possibly a second per page load on a busy server.
My recent experience with mediawiki is that php is such a slow beast anyway (even with APC) that connection/disconnect overhead is likely not to be significant. But it would still be a good idea for him to learn pgbouncer, in case his php code is much faster than mediawiki's is, or he runs into the spinlock contention inside postgresql that has been all the rage lately. It just isn't the first place I would look anymore.
