Re: UPDATEDs slowing SELECTs in a fully cached database

From: Greg Smith <greg(at)2ndQuadrant(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: UPDATEDs slowing SELECTs in a fully cached database
Date: 2011-07-18 00:44:03
Message-ID: 4E2381D3.9020201@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 07/16/2011 06:33 PM, Jeff Janes wrote:
> 2.6 ms for an fsync seems awfully quick. I wonder if EBS uses
> nonvolatile/battery-backed write cache, or if it just lies about fsync
> actually hitting disk.
>

They have the right type of cache in there to make fsync quick, when you
happen to be the lucky one to find it free of a write backlog. So the
best case is much better than a typical spinning drive with no such
cache. The worst case is in the 100ms+ range though on EBS.

--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Andy 2011-07-18 01:43:19 BBU still needed with SSD?
Previous Message lars 2011-07-17 02:12:47 Re: UPDATEDs slowing SELECTs in a fully cached database