RE: ORION num_disks

From: Allen, Brandon <>
Date: Fri, 12 Sep 2008 10:47:33 -0700
Message-ID: <04DDF147ED3A0D42B48A48A18D574C450D54291D@NT15.oneneck.corp>

From my experience, it seems that all num_disks does is increase the max load orion will run up to when you run with "-run simple/normal", or "-matrix basic/detailed" tests, for example, with num_disks 1 on a simple run, it will perform tests of single-block IOs at loads of 1,2,3,4,5 and then multi-block IOs at loads of 1 & 2. If you increase to num_disks 2, then it will run single-block IOs at loads 1,2,3,4,5,6,7,8,9,10 and multi-block at 1,2,3,4, and it just keeps going higher as you continue to increase num_disks. Beware it also takes much longer since each run takes 1 minute by default, however with the larger num_disks values, it does begin to skip data points, so, for example, instead of doing every point between 1-20, it will do something like 1,2,4,6,8,10,12,16,20.

In the case of an advanced run like you have below with a specific point of 45 large IOs and 0 small IOs, I don't think the num_disks parameter does anything, but please let me know if I'm wrong.


-----Original Message-----

[] On Behalf Of Greg Rahn

Normally it is set to the number of physical drives, but it can be adjusted higher or lower depending on how much load you want to drive.

-run advanced -type seq -testname thumper_seq -num_disks 45 -matrix
point -num_large 45 -num_small 0 -num_streamIO 16 -disk_start 0
-disk_end 150 -cache_size 0

Maximum Large MBPS=2668.88 @ Small=0 and Large=45

-- Received on Fri Sep 12 2008 - 12:47:33 CDT

Original text of this message