My apologies, I should've been much more explicit... This is for a specific
tablespace, with VERY static data...
> Size of data, size of stripe size/width are very important in detirmining
> how many spindles to use and if they will be effective. Using a
write-back
> caching controller (and not saturating it's cache) will generally write
out
> data trying to take advantage of the full stripe width. Reads are
effected
> in this manor as well.
Yeah...I'm thinking 80/20 Read/Write for Controller cache, but again, this
is not the puzzle
Case: one tablespace (regardless of how many datafiles) for data, one tbs
for indexes. 9 hard drives to deal with, with RAID 5 as level of choice.
Should DATA reside on 6-drive volume and indexes on separate 3-drive volume,
or should these two tbs live on same physical R5 volume?
Gary
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Gary Weber
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
