![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Call to arms: I: What is the better choice on x86_64,RHEL4u4(2.6x kernel), EMC CX300 SAN, EMC powerpath 4.5x, Oracle 10.2.0.3.0, RAC, ASM? 1) ASMlib accessing block dev, asynch i/o 2) Raw device access via /dev/raw/rawX II: Which i/o scheduler do you use with each respective technology stack? 1) CFQ 2) Deadline 3) No-OP 4) Anticipator III: Last question: Which parameter do you use for the above? 1) DISK_ASYNCH_IO 2) FILESYSTEMIO_OPTIONS |
#3
| |||
| |||
|
|
Call to arms: I: What is the better choice on x86_64,RHEL4u4(2.6x kernel), EMC CX300 SAN, EMC powerpath 4.5x, Oracle 10.2.0.3.0, RAC, ASM? 1) ASMlib accessing block dev, asynch i/o 2) Raw device access via /dev/raw/rawX |
#4
| |||
| |||
|
|
Call to arms: I: What is the better choice on x86_64,RHEL4u4(2.6x kernel), EMC CX300 SAN, EMC powerpath 4.5x, Oracle 10.2.0.3.0, RAC, ASM? 1) ASMlib accessing block dev, asynch i/o 2) Raw device access via /dev/raw/rawX II: Which i/o scheduler do you use with each respective technology stack? 1) CFQ 2) Deadline 3) No-OP 4) Anticipator III: Last question: Which parameter do you use for the above? 1) DISK_ASYNCH_IO 2) FILESYSTEMIO_OPTIONS |
![]() |
| Thread Tools | |
| Display Modes | |
| |