From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-general@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Questionaire: Common WAL write rates on busy servers.
Date: Fri, 28 Apr 2017 01:18:59 +0200
Message-ID: <8036f0b9-6bb9-d802-d301-53b488dea49f@2ndquadrant.com> (raw)
In-Reply-To: <20170427163407.dtqi6v57bj4tiu5c@alap3.anarazel.de>
References: <20170425041743.ddabv2mwevcmtx5a@alap3.anarazel.de>
<20170427155906.uudovtd62x56brmx@alap3.anarazel.de>
<a842fbdf-b761-bf21-47dd-cd87d05a8d04@commandprompt.com>
<20170427163407.dtqi6v57bj4tiu5c@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
On 04/27/2017 06:34 PM, Andres Freund wrote:
> On 2017-04-27 09:31:34 -0700, Joshua D. Drake wrote:
>> On 04/27/2017 08:59 AM, Andres Freund wrote:
>>
>>>
>>> Ok, based on the, few, answers I've got so far, my experience is
>>> indeed skewed. A number of the PG users I interacted with over
>>> the last couple years had WAL write ranges somewhere in the range
>>> of 500MB/s to 2.2GB/s (max I'veseen). At that point WAL insertion
>>> became a major bottleneck, even if storage was more than fast
>>> enough to keep up. To address these we'd need some changes, but
>>> the feedback so far suggest that it's not yet a widespread
>>> issue...
>>
>> I would agree it isn't yet a widespread issue.
>
> I'm not yet sure about that actually. I suspect a large percentage
> of people with such workloads aren't lingering lots on the lists.
>
To a certain extent, this is a self-fulfilling prophecy. If you know
you'll have such a busy system, you probably do some research and
testing first, before choosing the database. If we don't perform well
enough, you pick something else. Which removes the data point.
Obviously, there are systems that start small and get busier and busier
over time. And those are the ones we see.
cheers
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
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: tomas.vondra@2ndquadrant.com, andres@anarazel.de, jd@commandprompt.com, pgsql-general@postgresql.org
Subject: Re: [PERFORM] Questionaire: Common WAL write rates on busy servers.
In-Reply-To: <8036f0b9-6bb9-d802-d301-53b488dea49f@2ndquadrant.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