At PGCon 2009, Jesper Pedersen talked to me about the new Binary Transfer patch which was submitted to the JDBC Driver for Postgres 8.4. I thought it will be nice to compare how the JDBC 8.4 driver compared to older 8.3 JDBC Driver. Hence I took it for a drive

The 8.4 JDBC Driver with BinaryTransfer patch seems to get to a better peak faster but since to taper off at high clients. I don't know if this benchmark was the right benchmark for it. Need more benchmarks which uses JDBC to see the performance difference with this feature.


Comments:

it will be nice, to get a closeup where x>32

Posted by gregj on May 29, 2009 at 05:27 AM EDT #

Could you do a run with -Dorg.postgresql.forcebinary=true ?

Posted by jesperpedersen on May 29, 2009 at 06:58 AM EDT #

I don't think a TPM benchmark will reveal the benefit of binary transfer. Try reading lots of rows that contain dates.

Posted by Ken on September 01, 2009 at 05:48 PM EDT #

Hi Jignesh
I am using PGsql 8.4 and trying and apache commons dbcp connection pool with postgresql-8.2-504.jdbc3.jar driver.

My max-active connection is set to 20.
What is a typical recommended value of this params. Is it better to have a hundred's of connections. In the thread dump I see a whole bunch of threads in the 'Waiting' state?

Any thought?

Thanks
Vijay Kumar

Posted by Vijay Kumar on January 13, 2010 at 04:44 PM EST #

Hi Vijay,

I havent used apache commons dbcp a lot so hard for me to comment on it.. Typically max-active connections will really depend on how much each connection consume resources. So it is more of a try-measure-recallibrate approach here without really knowing details of what is running.

Posted by Jignesh Shah on January 13, 2010 at 04:55 PM EST #

Post a Comment:
  • HTML Syntax: NOT allowed

This blog copyright 2010 by Jignesh Shah