Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d3sqn-0000E2-2v for pgsql-general@arkaria.postgresql.org; Thu, 27 Apr 2017 23:29:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d3sqm-0002WP-2Z for pgsql-general@arkaria.postgresql.org; Thu, 27 Apr 2017 23:29:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d3sqj-0002QD-VU for pgsql-general@postgresql.org; Thu, 27 Apr 2017 23:29:26 +0000 Received: from mail-wm0-x22a.google.com ([2a00:1450:400c:c09::22a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1d3sqd-0004fQ-2G for pgsql-general@postgresql.org; Thu, 27 Apr 2017 23:29:24 +0000 Received: by mail-wm0-x22a.google.com with SMTP id w64so29203394wma.0 for ; Thu, 27 Apr 2017 16:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=O1qx6R14PoOyCjSAl3Sf4fv8/Rc18b4maNqRP3fveLk=; b=H2bGOFHNVxfZgR+TNIYa+99J8ml7NVC/MwgSM5/WeAaQnwvDQbE95RxNRxq8wxtVRW m7NuUXC46gCQo4pl4pEtepAubBYrEf3D9jCnUxXAmb/MuBRt9O4dLzlo2mRf5CbYYjDF DV6XYkvLJ4NHttKYIZY/YOZjouHNQnlDXoHeaHpzXAD5jPtQTszRu61i+K5+cwUMHYIa wlOO5hf5RTuda5DKTdcgmQTKhOo3Gu8UkfO281OpzecDkRDlWt+PZDlIRLHUIw+arcLs s3695toErli3FF9HzgamxSA64fUznQAJ3Iblbpqp4KVR7EeczkMqzgAsSZ47FodwBi2b bWIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=O1qx6R14PoOyCjSAl3Sf4fv8/Rc18b4maNqRP3fveLk=; b=ZW4XJHEHWGFhPjWv/JG+siFdFIGEnu2yDc72Q4hd0Dfhca1IDJL0LIeWfeTKtFSJVI hV5zzFzVOEHYld8KGcQxWdbsddE/QntKJxlqqKxWbaejsTELVQgC0dgcRTfw+I0VRFl4 SjwArO0HjaV9XckksFjchO+dHYC6TsmLy1xPjEpTLihCyE2+aYsGWZpydFW6OdSxki0i iOqL6n+mYPm8wlRhb4cXcUUvblVpq9EMmRvRXT10jtoz9QJVja+1y0BsI5KNKdGVxgQt pgcFJyZyy5d2++gYV5b90wiZ24vuJblvKqHNGjcHNCWO1lwUHTWOTH4QzUWK1AgxJ49R 8gxQ== X-Gm-Message-State: AN3rC/5gPZQb97iKN3lZfJIT3R+tKSZQz5wmlFDK8JgjdC4EXP9hwsiR qaxpi4Pwe04ClUju X-Received: by 10.28.58.21 with SMTP id h21mr3788507wma.9.1493335757266; Thu, 27 Apr 2017 16:29:17 -0700 (PDT) Received: from [10.137.2.17] (ip-89-177-46-65.net.upcbroadband.cz. [89.177.46.65]) by smtp.gmail.com with ESMTPSA id y63sm1153036wme.31.2017.04.27.16.29.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Apr 2017 16:29:16 -0700 (PDT) Subject: Re: [PERFORM] Questionaire: Common WAL write rates on busy servers. To: Andres Freund , "Joshua D. Drake" References: <20170425041743.ddabv2mwevcmtx5a@alap3.anarazel.de> <20170427155906.uudovtd62x56brmx@alap3.anarazel.de> <20170427163407.dtqi6v57bj4tiu5c@alap3.anarazel.de> <80f280c1-910f-7eae-33a2-fd0cfc9ee8c9@commandprompt.com> <20170427173540.fqaucmclpowfy5n7@alap3.anarazel.de> Cc: pgsql-general@postgresql.org, pgsql-performance@postgresql.org From: Tomas Vondra Message-ID: Date: Fri, 28 Apr 2017 01:29:14 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170427173540.fqaucmclpowfy5n7@alap3.anarazel.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 04/27/2017 07:35 PM, Andres Freund wrote: > On 2017-04-27 10:29:48 -0700, Joshua D. Drake wrote: >> On 04/27/2017 09:34 AM, 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: >>>> >> >>>> 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. >> >> That would probably be true. I was thinking of it more as the >> "most new users are in the cloud" and the "cloud" is going to be >> rare that a cloud user is going to be able to hit that level of >> writes. (at least not without spending LOTS of money) > > You can get pretty decent NVMe SSD drives on serveral cloud > providers these days, without immediately bancrupting you. Sure, it's > instance storage, but with a decent replication and archival setup, > that's not necessarily an issue. > > It's not that hard to get to the point where postgres can't keep up > with storage, at least for some workloads. > 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. regards -- 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