Greg Spiegelberg wrote:
I ran pgbench tests late last year comparing EC2, GoGrid, a 5 year-old lab server and a new server. Whether I used a stock postgresql.conf or tweaked, the current 8.4 or 9.0, or varied the EC2 instance size EC2 was always at the bottom ranging from 409.834 to 693.100 tps. GoGrid's pgbench TPS numbers in similar tests were, on average, 3X that of EC2 (1,399.550 to 1,631.887 tps). The tests I conducted were small with 10 connections and total 5,000 transactions. The single variable that helped pgbench tests in EC2 was to select an instance size where the number of cores was equal to or greater than the number of connections I used in the tests however this only improved things slightly (715.931 tps).
The standard pgbench test is extremely sensitive to how fast transactions can be committed to disk. That doesn't reflect what performance looks like on most real-world workloads, which tend toward more reads. The fact that GoGrid is much faster at doing commits than EC2 is interesting, but that's only one of many parameters that impact performance on more normal workloads.
The one parameter that can change how the test runs is turning off synchronous_commit, which pulls the commit time out of the results to some extent. And if you'd switched pgbench to a more read-oriented test, you'd discover it becomes extremely sensitive to the size of the database, as set by pgbench's scale parameter during setup.
-- Greg Smith 2ndQuadrant US greg@xxxxxxxxxxxxxxx Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
