pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Michael Stone <mstone+postgres@mathom.us>
To: pgsql-performance@postgresql.org
Subject: Re: Performance query about large tables, lots of concurrent access
Date: Mon, 25 Jun 2007 07:37:48 -0400
Message-ID: <20070625113746.GY19959@mathom.us> (raw)
In-Reply-To: <467AA77D.3030204@metacarta.com>
References: <4676DD57.7070304@metacarta.com>
	<20070620175300.GN30369@alvh.no-ip.org>
	<46796A08.8080601@metacarta.com>
	<200706201425.28557.sthomas@leapfrogonline.com>
	<46799C45.7080805@metacarta.com>
	<4679AE24.9070005@g2switchworks.com>
	<4679B6C7.3080207@metacarta.com>
	<467A9CE5.508@g2switchworks.com>
	<467AA77D.3030204@metacarta.com>

On Thu, Jun 21, 2007 at 12:29:49PM -0400, Karl Wright wrote:
>I checked the disk picture - this is a RAID disk array with 6 drives, 
>with a bit more than 1Tbyte total storage.  15,000 RPM.  It would be 
>hard to get more/faster disk than that.

Well, it's not hard to more disk than that, but you'd probably have to 
look at an external storage array (or more than one). A larger number of 
larger/slower drives, splitting indices away from data, etc., will 
almost certainly outperform 6 disks, 15k RPM or not.

Mike Stone



view thread (56+ messages)  latest in thread

Message-ID: <20070625113746.GY19959@mathom.us>
Permalink:  ../20070625113746.GY19959@mathom.us/
Also on:    postgresql.org/message-id/20070625113746.GY19959@mathom.us

 · 

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: mstone+postgres@mathom.us
  Subject: Re: Performance query about large tables, lots of concurrent access
  In-Reply-To: <20070625113746.GY19959@mathom.us>

* 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