From: Fernando Ike <fike@midstorm.org>
To: pgsql-performance@postgresql.org
Subject: Re: 8.3 synchronous_commit
Date: Mon, 21 Jan 2008 22:48:21 -0200
Message-ID: <20080121224821.22c2a800@pmanson> (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>
Em Mon, 21 Jan 2008 15:45:54 -0800
Jeff Davis <pgsql@j-davis.com> escreveu:
> On Mon, 2008-01-21 at 18:31 -0500, Greg Smith wrote:
> > pgbench doesn't handle 100 clients at once very well on the same
> > box as the server, unless you have a pretty serious system. The
> > pgbench program itself has a single process model that doesn't
> > handle the CFQ round-robin very well at all. On top of that, the
> > database scale should be bigger
>
> 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?
>
No. But pgbench local running, it will be concurrency with
PostgreSQL. I'm realized some test and really confirm disable
*synchronous_commit* performance degrade with CFQ and Deadline.
Kind Regards,
--
Fernando Ike
http://www.midstorm.org/~fike/weblog
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: fike@midstorm.org
Subject: Re: 8.3 synchronous_commit
In-Reply-To: <20080121224821.22c2a800@pmanson>
* 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