pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Slow count(*) again...
Date: Tue, 12 Oct 2010 12:03:57 -0400
Message-ID: <87iq179z4i.fsf@cbbrowne.afilias-int.info> (raw)
References: <201010091626.18636.neil.whelchel@gmail.com>
	<4CB11CC7.8070300@vmsinfo.com>
	<4CB167CA.9070109@postnewspapers.com.au>
	<4CB1F46E.80205@vmsinfo.com>
	<4CB2410C.6010603@postnewspapers.com.au>
	<4cb25a0e.2a978e0a.7797.33d6@mx.google.com>
	<4CB3C598.2010302@2ndquadrant.com>
	<AANLkTi=WE-CsGVC3j4CX9ddGGsRZ3Mmk6aJGKk4NT=g6@mail.gmail.com>
	<E2D86063-1FD0-48D0-BB0D-0E78F4A77FD2@richrelevance.com>
	<AANLkTimjsbV6W5JcMKs02b1wJLhhXaxHxq7=mURY50nG@mail.gmail.com>

sgendler@ideasculptor.com (Samuel Gendler) writes:
> Geez.  I wish someone would have written something quite so bold as
> 'xfs is always faster than ext3' in the standard tuning docs.  I
> couldn't find anything that made a strong filesystem
> recommendation.  How does xfs compare to ext4?  I wound up on ext4 on
> a dell perc6 raid card when an unexpected hardware failure on a
> production system caused my test system to get thrown into production
> before I could do any serious testing of xfs.  If there is a strong
> consensus that xfs is simply better, I could afford the downtime to
> switch.

It's news to me (in this thread!) that XFS is actually "getting some
developer love," which is a pretty crucial factor to considering it
relevant.

XFS was an SGI creation, and, with:

 a) the not-scintillating performance of the company,

 b) the lack of a lot of visible work going into the filesystem,

 c) the paucity of support by Linux vendors (for a long time, if you 
    told RHAT you were having problems, and were using XFS, the next
    step would be to park the ticket awaiting your installing a
    "supported filesystem")

it didn't look like XFS was a terribly good bet.  Those issues were
certainly causing concern a couple of years ago.

Faster "raw performance" isn't much good if it comes with a risk of:
 - Losing data
 - Losing support from vendors

If XFS now *is* getting support from both the development and support
perspectives, then the above concerns may have been invalidated.  It
would be very encouraging, if so.
-- 
output = ("cbbrowne" "@" "gmail.com")
Rules of  the Evil Overlord  #228.  "If the  hero claims he  wishes to
confess  in public  or to  me  personally, I  will remind  him that  a
notarized deposition will serve just as well."



view thread (246+ messages)  latest in thread

Message-ID: <87iq179z4i.fsf@cbbrowne.afilias-int.info>
Permalink:  ../87iq179z4i.fsf@cbbrowne.afilias-int.info/
Also on:    postgresql.org/message-id/87iq179z4i.fsf@cbbrowne.afilias-int.info

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: Slow count(*) again...
  In-Reply-To: <87iq179z4i.fsf@cbbrowne.afilias-int.info>
  References: <201010091626.18636.neil.whelchel@gmail.com> <4CB11CC7.8070300@vmsinfo.com> <4CB167CA.9070109@postnewspapers.com.au> <4CB1F46E.80205@vmsinfo.com> <4CB2410C.6010603@postnewspapers.com.au> <4cb25a0e.2a978e0a.7797.33d6@mx.google.com> <4CB3C598.2010302@2ndquadrant.com> <AANLkTi=WE-CsGVC3j4CX9ddGGsRZ3Mmk6aJGKk4NT=g6@mail.gmail.com> <E2D86063-1FD0-48D0-BB0D-0E78F4A77FD2@richrelevance.com> <AANLkTimjsbV6W5JcMKs02b1wJLhhXaxHxq7=mURY50nG@mail.gmail.com> <87iq179z4i.fsf@cbbrowne.afilias-int.info>

* 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