pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mladen Gogala <mladen.gogala@vmsinfo.com>
To: Scott Carey <scott@richrelevance.com>
Cc: " <pgsql-performance@postgresql.org>
Subject: Re: Slow count(*) again...
Date: Mon, 11 Oct 2010 22:23:46 -0400
Message-ID: <4CB3C6B2.8050501@vmsinfo.com> (raw)
In-Reply-To: <90E30938-1E5E-4DCA-A1FB-AEECEB76A70D@richrelevance.com>
References: <201010091626.18636.neil.whelchel@gmail.com>
	<4CB11CC7.8070300@vmsinfo.com>
	<4CB167CA.9070109@postnewspapers.com.au>
	<4CB1F46E.80205@vmsinfo.com>
	<90E30938-1E5E-4DCA-A1FB-AEECEB76A70D@richrelevance.com>

  On 10/11/2010 10:02 PM, Scott Carey wrote:
> Did you tune the linux FS read-ahead first?  You can get large gains by doing that if you are on ext3.
> blockdev --setra 2048<device>

Actually, I have blockdev --setra 32768

> would give you a 1MB read-ahead.  Also, consider XFS and its built-in defragmentation.  I have found that a longer lived postgres DB will get extreme
> file fragmentation over time and sequential scans end up mostly random.  On-line file defrag helps tremendously.

I agree, but I am afraid that after the demise of SGI, XFS isn't being 
developed. The company adopted the policy of using only the plain 
vanilla Ext3, which is unfortunate, but I can't do much about it. There 
is a lesson to be learned from the story of ReiserFS. I am aware of the 
fact that Ext3 is rather basic, block oriented file system which doesn't 
perform well when compared to HPFS, VxFS or JFS2 and has no notion of 
extents, but I believe that I am stuck with it, until the advent of 
Ext4. BTW, there is no defragmenter for Ext4, not even on Ubuntu, which 
is rather bleeding edge distribution.

-- 
Mladen Gogala
Sr. Oracle DBA
1500 Broadway
New York, NY 10036
(212) 329-5251
www.vmsinfo.com




view thread (246+ messages)  latest in thread

Message-ID: <4CB3C6B2.8050501@vmsinfo.com>
Permalink:  ../4CB3C6B2.8050501@vmsinfo.com/
Also on:    postgresql.org/message-id/4CB3C6B2.8050501@vmsinfo.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mladen.gogala@vmsinfo.com, scott@richrelevance.com
  Subject: Re: Slow count(*) again...
  In-Reply-To: <4CB3C6B2.8050501@vmsinfo.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