From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Questionaire: Common WAL write rates on busy servers. |
Date: | 2017-04-29 00:41:19 |
Message-ID: | 48afdba3-3429-de92-6fa8-36e2ebe5fd03@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On 04/28/2017 01:34 AM, Andres Freund wrote:
> On 2017-04-28 01:29:14 +0200, Tomas Vondra wrote:
>> I can confirm this observation. I bought the Intel 750 NVMe SSD last year,
>> the device has 1GB DDR3 cache on it (power-loss protected), can do ~1GB/s of
>> sustained O_DIRECT sequential writes. But when running pgbench, I can't push
>> more than ~300MB/s of WAL to it, no matter what I do because of
>> WALWriteLock.
>
> Hm, interesting. Even if you up wal_buffers to 128MB, use
> synchronous_commit = off, and play with wal_writer_delay/flush_after?
>
I think I've tried things like that, but let me do some proper testing.
I'll report the numbers in a few days.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2017-04-29 01:53:31 | Re: query planner placement of sort/limit w.r.t. joins |
Previous Message | David G. Johnston | 2017-04-28 23:37:00 | Re: query planner placement of sort/limit w.r.t. joins |
From | Date | Subject | |
---|---|---|---|
Next Message | jesse.hietanen | 2017-05-04 10:52:03 | Inefficient max query when using group by |
Previous Message | Andres Freund | 2017-04-27 23:34:33 | Re: Questionaire: Common WAL write rates on busy servers. |