On Fri, 26 Oct 2001, Andreas Dilger wrote: > However, it is also possible that striping across 26 disks is kind of > pointless, especially for Oracle. You are far better off to do some > intelligent allocation of the disks depending on known usage patterns > (e.g. put tables and their indexes on separate disks, put rollback > files on separate disks, put heavily used tables on their own disks, > put temporary tablespaces on their own disks). True. I have done that. This is a "let's see if it goes really fast with a lot of disks" test. We have the disks divided up in stripe sets no bigger than 8 typically, all separated out by function. I was just playing around with a massive stripe, and ran into this oddity.
