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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
