Thought I’d share some more information on ORION – ORacle I/O Numbers after I recently posted some brief notes here.
It seems that it’s not going to be available on the HP-UX which is unfortunate for my current project as that’s what we’re running on. Only Linux and Windows are available – it is beta, unsupported stuff after all though so fair play. I did hear something to the effect that it might be part of the RDBMS as of version 11 though so at that stage I guess it will cover all platforms – something to look forward to – perhaps it will be in Tom’s “Top 10” presentation next year ? 😉
After finally managing to get my SUSE Linux 10 up and running in Microsoft Virtual PC – albeit with only 512M of RAM to play with – I could try ORION out on there as well as on Windows…some highlights of the process…
Download all the ORION products (Windows and Linux) from here.
Download SUSE 10 Linux and installed it into a Microsoft Virtual PC VM.
Installed ORION under both SUSE linux and Microsoft XP platforms.
Windows XP (service pack 2 and updates)
Ran the orion10.2_windows.msi file to install the Windows version of ORION accepting all the defaults during the installation.
I don’t have raw partitions or logical volumes available on my Windows box so I tested the Windows port using files.
I pretty much followed the instructions in the acrobat document that comes with the product download. The only gotcha I encountered was that in trying to use files I discovered that unless the files were PPT, DOC or XLS I couldn’t get ORION to run – it simply complained and threw up a Microsoft Debug message. Unfortunately, a large number of adults suffer from erectile dysfunction, in which a man is unable to carry out the natural episodes of sexual performance in bed. buy cheap cialis click to find out The medicine is a vital product of Ajanta pharma and cialis 5 mg available at any authorized medical store. The semi liquid form of generic sildenafil is known to last for at least four hours and maximum 6 hours. buy levitra Remember that because of the old age you may little tasteless after taking the generic Apcalis, but I know that you will make that night an exceptional experience for your partner. tadalafil 20mg no prescription http://icks.org/n/data/ijks/1482456154_add_file_9.pdf As soon as I used one of the file types mentioned it worked fine. I did try renaming a text file to a .PPT but it didn’t work either so it really does need to be a proper MS Office type file it appears – either that’s very odd or I’m being thick and doing something extremely daft!
When I tried to use files on the SUSE Linux install it wouldn’t work with any type of files including these office ones so I’ve no idea how to use files on the Linux port – the raw lvm’s approach worked fine on there though.
Results of the simple run appeared in around 9 minutes showing:
Maximum Large MBPS=24.03 @ Small=0 and Large=2
Maximum Small IOPS=195 @ Small=4 and Large=0
Minimum Small Latency=5.42 @ Small=1 and Large=0
SUSE Linux 10
This was a bit more tricky as trying to run the ORION program immediately brought to my attention the fact that my linux install was missing a libaio library which I then had to research and install.
I downloaded the 0.3.0.version of libaio from technet here and tried to install it by running
./configure
…which then complained that it needed a version of libaio present to upgrade…so I downloaded one from Werner Puschitz here which helped me get libaio installed after a bit of effort.
OK after installing these files I had a working version of libaio and I was able to proceed with the use of ORION.
I set up 2 additional disks for the VM on different physical disks, then set up 2 volume groups (vg1 and vg2) with 1 logical volume per volume group (lv1 and lv2 respectively) so that I could test RAID v CONCAT. YAST was very easy to use in doing this I must say.
I created simple.lun with the following:
/dev/mapper/vg1-lv1
/dev/mapper/vg2-lv2
… and then ran the following command to get a simple test:
./orion10.2_linux –run simple –testname simple –num_disks 2
This gave the following results:
Maximum Large MBPS=8.73 @ Small=0 and Large=4
Maximum Small IOPS=80 @ Small=10 and Large=0
Maximum Small Latentcy=15.22 @ Small=1 and Large=0
I then created a file called dw_bench.lun with the following contents:
/dev/mapper/vg1-lv1
/dev/mapper/vg2-lv2
…and ran for datawarehouse advanced load using CONCAT using the following call:
./orion10.2_linux -run advanced -testname dw_bench -num_disks 2 -matrix point -num_small 0 -num_large 4 -type seq -num_streamIO 2 -simulate concat -cache_size 0 -verbose
…and got these results:
Maximum Large MBPS=9.61 @ Small=0 and Large=4
And then ran for RAID 0 with the following command:
./orion10.2_linux -run advanced -testname dw_bench -num_disks 2 -matrix point -num_small 0 -num_large 4 -type seq -num_streamIO 2 -simulate raid0 -cache_size 0 -verbose
And got these results:
Maximum Large MBPS=8.71 @ Small=0 and Large=4
Now, I tried without multiple sessions or parallel…
CONCAT 1 large, 1 parallel stream IO
Maximum Large MBPS=8.83 @ Small=0 and Large=1
RAID0 1 large, 1 parallel stream IO
Maximum Large MBPS=8.23 @ Small=0 and Large=1
That’s all the results I have for now – at least it’s working after much tinkering.
I was a little perplexed by the fact that the CONCAT performance seemed better than the RAID 0 – pretty similar figures and maybe it’s to do with running on a VM – the difference between the VM figures and the native XP run showed the VM was about 3 times as slow.
One day I might work out why this is so….but that would require me to have two spare minutes to rub together!