Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Raw Devices v.s. File System
Michael,
If you are not running Oracle Parallel Server, believe me when I tell you that you will get comparable performance using Veritas vxfs file systems as compared to Raw Devices. There have been enough benchmarks and real-life production configurations that have been done to prove this. Been there...done that. It is not worth dealing with "raw devices" if you have an advanced file system such as Veritas with an I/O driver that facilitates "non-buffered I/O". This takes care of the "double buffering" problem that is prevelant with normal ufs filesystems.
In addition to configuring vxfs filesystems you need to install and configure the "Database Accelerator" - "Quick I/O for Oracle" component of Veritas. This simulates the effects of "non-buffered I/O". Basically, while configuring the file systems, the Quick I-O tag is put on it (so to speak) and this assists the driver in identifying "Quick I/O" calls to that filesystem and intercepting it. It does it by "bypassing" the file system buffercache and performing it directly from the device. So you have "raw device" comparable performance, without sacrificing the benefits of a cooked filesystem.
To minimize the overhead in filesystem-database block size mapping, keep the vxfs filesystem block size (default 8k) and the db_block_size of the database to the same. Then configure your Oracle database, just as usual. Leave the rest to Quick I/O, it does pretty well. There are white papers at www.veritas.com on Quick I/O and Oracle and how it works.
Cheers,
Gaja.
"Opinions and views expressed are my own and not of Quest"
![]() |
![]() |