From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brian Hurt <bhurt@janestcapital.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Some performance numbers, with thoughts
Date: Mon, 19 Jun 2006 21:17:19 -0400
Message-ID: <23027.1150766239@sss.pgh.pa.us> (raw)
In-Reply-To: <44973CC6.20309@janestcapital.com>
References: <44973CC6.20309@janestcapital.com>
Brian Hurt <bhurt@janestcapital.com> writes:
> For long involved reasons I'm hanging out late at work today, and rather
> than doing real, productive work, I thought I'd run some benchmarks
> against our development PostgreSQL database server. My conclusions are
> at the end.
Ummm ... you forgot to mention Postgres version? Also, which client and
server encodings did you use (that starts to get to be a noticeable
issue for high COPY rates)?
> 1) Transaction time is a huge hit on the small block sizes.
Right. For small transactions with a drive honoring fsync, you should
expect to get a max of about one commit per platter revolution. Your
numbers work out to a shade under 5000 commits/minute, from which I
speculate a 7200 RPM drive ... do you know what it really is?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, bhurt@janestcapital.com
Subject: Re: Some performance numbers, with thoughts
In-Reply-To: <23027.1150766239@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox