pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Klaus P. Pieper <kpi6288@gmail.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: pgbench Windows outperforms Debian in Write tests while Debian is faster in SELECT only tests
Date: Mon, 29 May 2017 21:59:43 +0200
Message-ID: <006401d2d8b6$1e889240$5b99b6c0$@gmail.com> (raw)
In-Reply-To: <12144.1496074592@sss.pgh.pa.us>
References: <028501d2d84f$2f1ea840$8d5bf8c0$@gmail.com>
	<31836.1496045941@sss.pgh.pa.us>
	<030801d2d87b$4f556820$ee003860$@gmail.com>
	<12144.1496074592@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

> Von: Tom Lane 

> Gesendet: Montag, 29. Mai 2017 18:17

> 

> OK, so open_datasync and fdatasync are nonfunctional on Windows, which is

> unsurprising.  The other cases are evidently doing *something*, but the
amount

> of overhead is variable from one sync method to another, which is likewise

> unsurprising.  The whole reason why we have these options at all is that
some

> systems handle some of them better than others.  In this case, I think the

> relevant conclusion is that correct configuration for Debian is to use

> open_datasync or fdatasync, while correct configuration for Windows is to
use

> fsync or fsync_writethrough, and when you compare those two
configurations,

> yes Windows is slower.

 

Excellent answer, thanks. 

 

Correct me if I'm wrong: I understand that synchronous_commit = off in
combination with fdatasync (Debian) or fsync_writethrough (Windows) is
"safe" (for regular interactive desktop applications).

 

These options gave the following results:

 

                         Windows        Debian

40 clients READ/WRITE       5400          7400   

1 client READ/WRITE          400           390

 

Single client READ/WRITE tests are on now the same level. In the multi
client test, Debian is performing significantly better than Windows. 

 

> 

> If you're a paranoid sort you would want to do plug-pull testing to ensure
that

> your selected setting actually does prevent data corruption during a
system

> crash.

 

That's certainly an option before we take this into production. 

 

Regards Klaus



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

view thread (8+ messages)  latest in thread

Message-ID: <006401d2d8b6$1e889240$5b99b6c0$@gmail.com>
Permalink:  ../006401d2d8b6$1e889240$5b99b6c0$@gmail.com/
Also on:    postgresql.org/message-id/006401d2d8b6$1e889240$5b99b6c0$@gmail.com

 · 

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-admin@postgresql.org
  Cc: kpi6288@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: pgbench Windows outperforms Debian in Write tests while Debian is faster in SELECT only tests
  In-Reply-To: <006401d2d8b6$1e889240$5b99b6c0$@gmail.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