pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Milen Kulev <makulev@gmx.net>
To: 'Mikael Carneholm' <Mikael.Carneholm@WirelessCar.com>
To: pgsql-performance@postgresql.org
Subject: Re: RAID stripe size question
Date: Tue, 18 Jul 2006 22:01:27 +0200
Message-ID: <001a01c6aaa4$f45aaee0$0a00a8c0@trivadis.com> (raw)
In-Reply-To: <7F10D26ECFA1FB458B89C5B4B0D72C2B4E4BFA@sesrv12.wirelesscar.com>

According to http://www.pcguide.com/ref/hdd/perf/raid/concepts/perfStripe-c.html, it seems to be the other way around?
("As stripe size is decreased, files are broken into smaller and smaller pieces. This increases the number of drives
that an average file will use to hold all the blocks containing the data of that file, 

->>>>theoretically increasing transfer performance, but decreasing positioning performance.")

Mikael,
In OLTP you utterly need  best possible latency.  If you decompose the response time if you physical request you will
see positioning performance plays the dominant role in the response time (ignore for a moment caches and their effects).

So, if you need really good response times of your SQL queries, choose  15 rpm disks(and add as much cache as possible
to magnify the effect ;) )

Best Regards. 
Milen 




view thread (28+ messages)  latest in thread

Message-ID: <001a01c6aaa4$f45aaee0$0a00a8c0@trivadis.com>
Permalink:  ../001a01c6aaa4$f45aaee0$0a00a8c0@trivadis.com/
Also on:    postgresql.org/message-id/001a01c6aaa4$f45aaee0$0a00a8c0@trivadis.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: makulev@gmx.net, Mikael.Carneholm@WirelessCar.com
  Subject: Re: RAID stripe size question
  In-Reply-To: <001a01c6aaa4$f45aaee0$0a00a8c0@trivadis.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