pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Mkrtchyan, Tigran <tigran.mkrtchyan@desy.de>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: postgres 9.3 vs. 9.4
Date: Thu, 25 Sep 2014 16:39:40 +1200
Message-ID: <54239C8C.6010902@catalyst.net.nz> (raw)
In-Reply-To: <327866330.127797.1411563803777.JavaMail.zimbra@desy.de>
References: <45142416.42827.1411033201079.JavaMail.zimbra@desy.de>
	<212134052.46894.1411111441514.JavaMail.zimbra@desy.de>
	<541CC338.5090700@catalyst.net.nz>
	<CAHyXU0zj8P41G-5QpL2Lz-DYLtfsqQP3TbR3pLTFhUUuYg8ekQ@mail.gmail.com>
	<1234976322.60875.1411477085811.JavaMail.zimbra@desy.de>
	<CAHyXU0yOfJ1mj2W0mBd==-hO260g8vtC7=-ptORnR2pfymShyA@mail.gmail.com>
	<1160757821.126570.1411550628851.JavaMail.zimbra@desy.de>
	<5422971C.3090501@catalyst.net.nz>
	<327866330.127797.1411563803777.JavaMail.zimbra@desy.de>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

On 25/09/14 01:03, Mkrtchyan, Tigran wrote:
>
> With pg_test_timing I can see, that overhead is 48 nsec on my server and 32 nsec on the laptop.
> what makes this difference and have it any influence on the overall performance?
>

Hmm - 22 nsec for my workstation, so while it could be a factor, your 
laptop and my workstation performed the pgbench about the same, so I'd 
look elsewhere - in particlular sync IO performance:


$ cd <where ssd mounted>
$ pg_test_fsync
5 seconds per test
O_DIRECT supported on this platform for open_datasync and open_sync.

Compare file sync methods using one 8kB write:
(in wal_sync_method preference order, except fdatasync
is Linux's default)
         open_datasync                       140.231 ops/sec    7131 
usecs/op
         fdatasync                           138.159 ops/sec    7238 
usecs/op
         fsync                               137.680 ops/sec    7263 
usecs/op
         fsync_writethrough                              n/a
         open_sync                           137.202 ops/sec    7289 
usecs/op

Compare file sync methods using two 8kB writes:
(in wal_sync_method preference order, except fdatasync
is Linux's default)
         open_datasync                        68.832 ops/sec   14528 
usecs/op
         fdatasync                           135.994 ops/sec    7353 
usecs/op
         fsync                               137.454 ops/sec    7275 
usecs/op
         fsync_writethrough                              n/a
         open_sync                            69.092 ops/sec   14473 
usecs/op

Compare open_sync with different write sizes:
(This is designed to compare the cost of writing 16kB
in different write open_sync sizes.)
          1 * 16kB open_sync write           136.904 ops/sec    7304 
usecs/op
          2 *  8kB open_sync writes           68.857 ops/sec   14523 
usecs/op
          4 *  4kB open_sync writes           34.744 ops/sec   28782 
usecs/op
          8 *  2kB open_sync writes      write failed: Invalid argument



-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (30+ messages)

Message-ID: <54239C8C.6010902@catalyst.net.nz>
Permalink:  ../54239C8C.6010902@catalyst.net.nz/
Also on:    postgresql.org/message-id/54239C8C.6010902@catalyst.net.nz

 · 

reply

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: mark.kirkwood@catalyst.net.nz, tigran.mkrtchyan@desy.de, mmoncure@gmail.com
  Subject: Re: postgres 9.3 vs. 9.4
  In-Reply-To: <54239C8C.6010902@catalyst.net.nz>

* 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