> why is it useful to seperate different i/o pattersn? such as > multi-block reads and single block reads?
Because (assuming adaptive I/O subsystems like EMC's and such) each gets optimized into different priority scales and device queues. And of course if they are to the same device, they *may* interfere with each other. Like I said: highly dependent on your I/O hardware. Doesn't hurt to set it up so you can take advantage of any future expansion/upgrade. IOW, separate indexes and tables into individual tablespaces, not because of I/O performance considerations but because of the flexibility it gives you in adapting to future change. The core of the OFA paper, really. But I'll let Cary speak for that: it's his baby. Cheers Nuno Souto [EMAIL PROTECTED] -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Nuno Pinto do Souto INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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).
