From: Greg Smith <greg@2ndquadrant.com>
To: Scott Carey <scott@richrelevance.com>
Cc: " <david@lang.hm>
Cc: " <david@lang.hm>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Francisco Reyes <lists@stringsutils.com>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: 10K vs 15k rpm for analytics
Date: Tue, 09 Mar 2010 02:00:50 -0500
Message-ID: <4B95F222.6040504@2ndquadrant.com> (raw)
In-Reply-To: <06A22EB5-2D84-401C-B75F-7CA883695E0A@richrelevance.com>
References: <cone.1267562557.293175.32557.1000@shelca>
<dcc563d11003021312k57e9c558n177e10ad16ab32b1@mail.gmail.com>
<cone.1267565429.453229.32557.1000@shelca>
<dcc563d11003021347h52f94812jf75b5937937a9ed4@mail.gmail.com>
<alpine.DEB.2.00.1003021408340.5131@asgard.lang.hm>
<06A22EB5-2D84-401C-B75F-7CA883695E0A@richrelevance.com>
Scott Carey wrote:
> For high sequential throughput, nothing is as optimized as XFS on Linux yet. It has weaknesses elsewhere however.
>
I'm curious what you feel those weaknesses are. The recent addition of
XFS back into a more mainstream position in the RHEL kernel as of their
5.4 update greatly expands where I can use it now, have been heavily
revisiting it since that release. I've already noted how well it does
on sequential read/write tasks relative to ext3, and it looks like the
main downsides I used to worry about with it (mainly crash recovery
issues) were also squashed in recent years.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us
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: greg@2ndquadrant.com, scott@richrelevance.com, david@lang.hm, scott.marlowe@gmail.com, lists@stringsutils.com
Subject: Re: 10K vs 15k rpm for analytics
In-Reply-To: <4B95F222.6040504@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