From: Steve Francis <sfrancis@logicmonitor.com>
To: pgsql-admin@postgresql.org
Subject: Re: Best Linux filesystem for Postgres data store ?
Date: Wed, 01 Dec 2010 08:05:47 -0800
Message-ID: <4CF6725B.2050004@logicmonitor.com> (raw)
In-Reply-To: <4CF61B430200002500038009@gw.wicourts.gov>
References: <AANLkTinnJhU49CQoD36F9dPRpPg+2inVCGP-jBV7dgny@mail.gmail.com>
<4CF61B430200002500038009@gw.wicourts.gov>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 12/1/2010 7:54 AM, Kevin Grittner wrote:
<blockquote cite="mid:4CF61B430200002500038009@gw.wicourts.gov"
type="cite"><br>
<pre wrap="">
Your RAID configuration and controllers will likely make a bigger
difference than your filesystem choices. Be sure to get good RAID
controllers with battery-backed (BBU) cache, configured for
write-back.
</pre>
</blockquote>
I agree that storage makes a bigger difference than filesystems in
most cases.<br>
Just wanted to jump in and say that testing with your workload is
really the only way to know things for sure. (Obviously, more
spindles implies more IOps, more cache implies faster writes...)<br>
But I have seen cases where a dell PERC RAID controller (not sure
that qualifies as "good") slowed things down when configured for
writeback with a write heavy workload. We noticed very spiky disk IO
rates on some database servers (we are monitoring company, so have
lots and lots of pretty graphs.) The controller seemed to accept a
bunch of writes quickly, then when full then try to pump them all to
disk, which took a non-trivial number of seconds. So we'd see the
interesting state of iostat reporting zero disk transactions per
second, but busy time = 100% and service time being hundreds of
millseconds.<br>
Switching to write through made things much faster overall. Not what
I expected.<br>
<br>
This was a PERC 5, so a few years ago. No doubt things have
improved, but the point is to test and monitor.<br>
<br>
<div class="moz-signature">-- <br>
<style type="text/css"> .sig, .sig a, .sig td { font: 12px Arial; color: DarkBlue; white-space: nowrap; vertical-align: top; text-align: left; } .sig img { border: 0; } .sig a { font: 11px Arial; } .sig .back { color: #ffffff; background-color: DarkBlue; text-decoration: none; } .sig .right { text-align: right; } .sig .border { border: 1px solid DarkBlue; margin:5px; border-collapse: collapse; } .sig .bottom { vertical-align:bottom } .sig p { clear:both; margin:2px; } </style>
<div class="sig">
<table class="border">
<tbody>
<tr>
<td class="back"> <b>Steve Francis</b></td>
<td class="back" style="width: 30px;"><br>
</td>
<td class="back" style="text-align: right;"><b>LogicMonitor
LLC</b></td>
</tr>
<tr>
<td><br>
</td>
<td><br>
</td>
<td class="right"><br>
</td>
</tr>
<tr>
<td class="bottom"><a class="moz-txt-link-abbreviated" href="mailto:sfrancis@logicmonitor.com">sfrancis@logicmonitor.com</a><br>
<a target="_blank" href="http://www.logicmonitor.com">www.logicmonitor.com</a></td;
<td><br>
</td>
<td class="bottom" style="text-align: right;"> Ph: 1 888
41 LOGIC x500<br>
Ph: 1 805 698 0770</td>
</tr>
</tbody>
</table>
<p> <br>
</p>
</div>
</div>
</body>
</html>
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-admin@postgresql.org
Cc: sfrancis@logicmonitor.com
Subject: Re: Best Linux filesystem for Postgres data store ?
In-Reply-To: <4CF6725B.2050004@logicmonitor.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