Re: Can a Mysql MyISAM or InnoDB table benefit from the STRIPE feature of disk device?

[Rick James]

If a single physical drive can be broken into logical drives, and then you arrange for the logical drives to be stripes?? -- well, this sounds, bluntly, stupid. Writing consecutive blocks ("block" size may be a function of how the striping works) requires arm motion. And it is probably a large arm motion.

Striping across multiple drives is good. Consecutive blocks hit different drives. If the readahead logic is smart, it might even get multiple drives helping in a single streaming of data. Random accesses by separate queries (eg, fetching a single row) will sometimes hit different physical drives, thereby interfering less with each other.

I am against the old logic of "put xxx on one drive; yyy on another". You are almost always better off striping those two drives together and letting the reads/writes land where they may.

In particular the old logic of "put indexes on one drive, data on another", is really misguided. A typical SELECT first reads the index, then reads the data -- no overlap! (OK, that is a simplification.)