From: Greg Smith <gsmith@gregsmith.com>
To: pgsql-performance@postgresql.org
Subject: Re: 8.3 synchronous_commit
Date: Mon, 21 Jan 2008 19:26:14 -0500 (EST)
Message-ID: <Pine.GSO.4.64.0801211912340.10359@westnet.com> (raw)
In-Reply-To: <1200959154.10057.533.camel@dogma.ljc.laika.com>
References: <fn34ca$2ff8$1@news.hub.org>
<Pine.GSO.4.64.0801211809410.27994@westnet.com>
<1200959154.10057.533.camel@dogma.ljc.laika.com>
On Mon, 21 Jan 2008, Jeff Davis wrote:
> He was referring to the CFQ I/O scheduler. I don't think that will
> affect pgbench itself, because it doesn't read/write to disk, right?
It does if you are writing latency log files but it shouldn't be in the
cases given. But there's something weird about the interplay between the
server disk I/O under CFQ and the time slices the pgbench client gets when
they're all on the same system. pgbench is certainly a badly scaling (in
regards to how it handles simulating many clients) single process utility
and anything that starves its execution sometimes is deadly. I never dug
deep into the exact scheduler issues, but regardless in this case it's
kind of unrealistic for Hannes to expect to simulate 100 clients on a
small system and still get a true view of how the server on that system
performs.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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: gsmith@gregsmith.com
Subject: Re: 8.3 synchronous_commit
In-Reply-To: <Pine.GSO.4.64.0801211912340.10359@westnet.com>
* 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