From: Hannes Dorbath <light@theendofthetunnel.de>
To: Greg Smith <gsmith@gregsmith.com>
Subject: Re: 8.3 synchronous_commit
Date: Tue, 22 Jan 2008 13:13:57 +0100
Message-ID: <4795DE05.7060109@theendofthetunnel.de> (raw)
In-Reply-To: <Pine.GSO.4.64.0801211809410.27994@westnet.com>
References: <fn34ca$2ff8$1@news.hub.org>
<Pine.GSO.4.64.0801211809410.27994@westnet.com>
Greg Smith wrote:
> Try something more in the range of 4 clients/CPU and set the scale to
> closer to twice that (so with a dual-core system you might do 8 clients
> and a scale of 16). If you really want to simulate a large number of
> clients, do that on another system and connect to the server remotely.
With 4 clients and scale 10 I get 246 TPS for synchronous_commit
disabled and 634 TPS for synchronous_commit enabled. So the effect just
got even stronger. That was for CFQ.
For deadline they are now pretty close, but synchronous_commit disabled
is still slower. 690 to 727.
Values are AVG from 3 runs each. DROP/CREATE DATABASE and CHECKPOINT;
before each run.
--
Best regards,
Hannes Dorbath
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: light@theendofthetunnel.de, gsmith@gregsmith.com
Subject: Re: 8.3 synchronous_commit
In-Reply-To: <4795DE05.7060109@theendofthetunnel.de>
* 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