From: Andrea Suisani <sickpig@opinioni.net>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: Reliability with RAID 10 SSD and Streaming Replication
Date: Thu, 23 May 2013 15:55:08 +0200
Message-ID: <519E1FBC.9020409@opinioni.net> (raw)
In-Reply-To: <CAHyXU0wp-m3nD4S_+5_fuPRyK82QgOg=p-kh51wiLSk9_Mkqyw@mail.gmail.com>
References: <CAAE-9WHMycEZOB5J6HKME5AZLEdL2hYF+FV8hzbLksJinq=EJg@mail.gmail.com>
<51957499.6050905@fuzzy.cz>
<519991EB.8010208@2ndQuadrant.com>
<519A8E29.60702@fuzzy.cz>
<CAHyXU0wvW-USgbkXAYEHLG2fHgj=UdZi1aCFoVWBMQEsOFZy+A@mail.gmail.com>
<519C0EFD.9080002@2ndQuadrant.com>
<CAHyXU0ymFT7Sqw77yPryGWKEpjV4Wv9Vkc21vGtPKo0GZWGg8A@mail.gmail.com>
<519DBDB2.2050106@opinioni.net>
<CAHyXU0wp-m3nD4S_+5_fuPRyK82QgOg=p-kh51wiLSk9_Mkqyw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 05/23/2013 03:47 PM, Merlin Moncure wrote:
[cut]
>> <quote>
>>
>> [..] There are two components to the Swingbench test we're running here:
>> the database itself, and the redo log. The redo log stores all changes that
>> are made to the database, which allows the database to be reconstructed in
>> the event of a failure. In good DB design, these two would exist on separate
>> storage systems, but in order to increase IO we combined them both for this
>> test.
>> Accesses to the DB end up being 8KB and random in nature, a definite strong
>> suit
>> of the S3700 as we've already shown. The redo log however consists of a
>> bunch
>> of 1KB - 1.5KB, QD1, sequential accesses. The S3700, like many of the newer
>> controllers we've tested, isn't optimized for low queue depth, sub-4KB,
>> sequential
>> workloads like this. [..]
>>
>> </quote>
>>
>> Does this kind of scenario apply to postgresql wal files repo ?
>
> huh -- I don't think so. wal file segments are 8kb aligned, ditto
> clog, etc. In XLogWrite():
>
> /* OK to write the page(s) */
> from = XLogCtl->pages + startidx * (Size) XLOG_BLCKSZ;
> nbytes = npages * (Size) XLOG_BLCKSZ; <--
> errno = 0;
> if (write(openLogFile, from, nbytes) != nbytes)
> {
>
> AFICT, that's the only way you write out xlog. One thing I would
> definitely advise though is to disable partial page writes if it's
> enabled. s3700 is algined on 8kb blocks internally -- hm.
many thanks merlin for both the explanation and the good advice :)
andrea
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: sickpig@opinioni.net, mmoncure@gmail.com, greg@2ndquadrant.com, tv@fuzzy.cz
Subject: Re: Reliability with RAID 10 SSD and Streaming Replication
In-Reply-To: <519E1FBC.9020409@opinioni.net>
* 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