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.")
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 ;) )
In response to
pgsql-performance by date
|Next:||From: Guoping Zhang||Date: 2006-07-19 05:40:02|
|Subject: Performance penalty for remote access of postgresql (8.1.3)? any experiance?|
|Previous:||From: Scott Marlowe||Date: 2006-07-18 19:48:46|
|Subject: Re: RAID stripe size question|