These aren't formal benchmarks but, having just tried it on one of our
development systems, I can tell you that Apache2::DBI without pgbouncer is
slower than using pgbouncer without Apache2::DBI. Although, using both
seems to be marginally faster than either.
On Tue, Apr 22, 2014 at 12:36 PM, Per
Apache::DBI overrides DBI's connect() method so that you're using
persistent connections when you use DBI directly. It may be that your
performance improvement came from better management of Pg resources
with PgBouncer than from reducing connection overhead. You could test
it be removing Apache::
use Apache::DBI (); appears in our startup.pl but the application code uses
DBI directly.
On Tue, Apr 22, 2014 at 12:30 PM, Perrin Harkins wrote:
> Thanks John. Were you using Apache::DBI before PgBouncer?
> Apache::DBI would also eliminate the overhead of establishing new
> connections.
>
> -
Thanks John. Were you using Apache::DBI before PgBouncer?
Apache::DBI would also eliminate the overhead of establishing new
connections.
- Perrin
On Tue, Apr 22, 2014 at 12:23 PM, John Dunlap wrote:
> I can speak to your final point. I recently deployed PGBouncer into our
> production environme
I can speak to your final point. I recently deployed PGBouncer into our
production environment and, like the OP, we have separate web and database
servers. With PGBouncer running on the web server(you could also run it on
the database server if you wanted to) we noticed a dramatic increase in
perfo
Interesting. Why did you have to install PgBouncer? Can't Postgres
handle remote connections from your web server?
I don't use Postgres, but reading the description of PgBouncer I can
see some things you'd want to consider.
First, Apache::DBI prevents you from making persistent connections
befo
Apache::DBI caches database connection per process so you avoid the cost of
creating a connection on each requests.
Pgbouncer pools database connections so that you don't tie up one
postmaster process per httpd process.
If you only have one webserver you may not have a real need for pgbouncer;
it
I'd be interested in hearing about this too.
On Tue, Apr 22, 2014 at 10:02 AM, jbiskofski wrote:
> I just want to confirm something with all you smart folks.
>
> I recently separated my web servers from my database servers, before I was
> using Apache::DBI to maintain persistent connections bet
I just want to confirm something with all you smart folks.
I recently separated my web servers from my database servers, before I was
using Apache::DBI to maintain persistent connections between Apache and
Postgres. With this new setup I had to install PgBouncer. Can I now safely
remove Apache::DB