pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: pg@fastcrypt.com
Cc: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: 29 Mar 2005 13:11:04 -0500
Message-ID: <87ekdyz5jb.fsf@stark.xeocode.com> (raw)
In-Reply-To: <42494741.7060806@fastcrypt.com>
References: <42443863.4040302@sfnet.cc>
	<4244A90B.2030200@sfnet.cc>
	<42453273.2060509@turtle-entertainment.de>
	<200503261255.59007.josh@agliodbs.com>
	<42455DEC.2080301@sfnet.cc>
	<1112049794.23284.29.camel@localhost.localdomain>
	<424840AE.3050200@sfnet.cc>
	<op.sod768rgth1vuj@localhost>
	<42494741.7060806@fastcrypt.com>


Dave Cramer <pg@fastcrypt.com> writes:

> PFC wrote:
> >
> >     My Laptop does 19 MB/s (reading <10 KB files, reiser4) !
>
> Yeah, 35Mb per sec is slow for a raid controller, the 3ware mirrored is
> about 50Mb/sec, and striped is about 100

Well you're comparing apples and oranges here. A modern 7200rpm drive should
be capable of doing 40-50MB/s depending on the location of the data on the
disk. 

But that's only doing sequential access of data using something like dd and
without other processes intervening and causing seeks. In practice it seems a
busy databases see random_page_costs of about 4 which for a drive with 10ms
seek time translates to only about 3.2MB/s.

I think the first order of business is getting pg_xlog onto its own device.
That alone should remove a lot of the seeking. If it's an ext3 device I would
also consider moving the journal to a dedicated drive as well. (or if they're
scsi drives or you're sure the raid controller is safe from write caching then
just switch file systems to something that doesn't journal data.)


-- 
greg




view thread (119+ messages)  latest in thread

Message-ID: <87ekdyz5jb.fsf@stark.xeocode.com>
Permalink:  ../87ekdyz5jb.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87ekdyz5jb.fsf@stark.xeocode.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: gsstark@mit.edu, pg@fastcrypt.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <87ekdyz5jb.fsf@stark.xeocode.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