Hi - as you can see in your results the xdisk tool with 1 MB block size drove the V7000 up to 3.4 Gigabytes per second.
The reason I mentioned using 0x40000 for the hdisk max_transfer is because that is what the SDDPCM driver used by default and I have seen better V7000 performance with this value compared to the 0x80000 default that AIX MPIO uses.
You can leave the FC adapter at 0x100000 or you could change it to 0x200000. This tunable is independent of the hdisk one.
If you do reduce the hdisk max_transfer from 0x80000 to 0x40000 you can then compare the xdisk results now that you have already run it once.
Thanks
Dean
--- Post updated at 09:05 PM ---
Regarding your question of tuning max_xfer_size you can do it dynamically assuming your LUN's have multiple paths. (lspath to confirm)
can someone tell me a good site to go to in order to learn this. please do not recommen nay books because i dont have interest in that. if you know of any good sites with good straight forward explanation on how to split loads on machines that has excessive loading, please let me know
Also,... (1 Reply)
Hi all,
long time ago I posted something, but now, it is needed again :(
Currently, I am handling with a big NFS Server for more than 200 clients, this sever has to work with 256 NFSDs. Because of this huge amount of NFSDs, there are thousands of small write accesses down to the disk and... (3 Replies)
Hi to all,
I'm interested in finding an introduction about Performance Tuning under Unix (or Linux); can somebody please point me in the right direction?
Best regards (1 Reply)
Sorry,
This is out of scope of this group.But I require the clarification pretty urgently.
My Oracle database is parallely enabled.
Still,in a particular table queries do not work "parallely" always.
How is this? (9 Replies)
Hi All,
In last one week, i have posted many questions in this portal. At last i am succeeded to make my 1st unix script.
following are 2 points where my script is taking tooooo long.
1. Print the total number of records excluding header & footer. I have found that awk 'END{print NR -... (2 Replies)
Hi all,
From Googling, I found that the basics used for troubleshooting UNIX/AIX performance issues are commands like vmstat, iostat and sar. I believe these are generic commands regardless of what UNIX flavour is in used, only difference being is the format of the output.
In a real case... (2 Replies)
Please take a look at this system and give your analysis / advice. Can it be tuned to get a better performance?
We are not getting more hardware ressources at the moment.
We have to live with what we have. Application running on the system is SAS. OS is AIX 6.1
Let me know if you need output of... (7 Replies)
Dear all,
I have a Local zone , where users feel that performance is not good.
Is it wise to collect the inputs from the local zone rather than taking from the global zone.
And also Can I tune from Global zone , so that it will reflect in local zone.
Rgds
rj (2 Replies)
Overview:
Introduction
What Does Success Mean?
What Does Performance Mean?
Every Picture is Worth a Thousand Words
Work Like a Physicist
Work Like You Walk - One Step at a Time
Learn to Know Your System
Choose Your Weapons!
Tools of the Trade 1 - vmstat
A Little Theory Along the Way -... (1 Reply)
Discussion started by: bakunin
1 Replies
LEARN ABOUT HPUX
iobind
iobind(1M)iobind(1M)NAME
iobind - bind a driver to a device
SYNOPSIS
instance]
DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it.
As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware
paths.
The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will
be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated
with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The
optional forces the binding to occur at the next reboot if it cannot be done online.
The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of
these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The
user is given the option to proceed or not.
If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown
by the command:
The specified driver was successfully bound to the hardware path.
The specified driver cannot be used to claim the hardware at
the specified hardware path.
The device at the address is responding, but it is in an
error state.
The device at the specified hardware path is no longer responding.
The specified hardware path is locked. Try again later.
The driver failed.
Options
recognizes the following options:
Force the binding even though a driver does not support online unbinding
and binding or the device is in use. In this case, the binding will take effect at the next reboot.
The LUN hardware path of a device
must be of the form 64000/0x/0x.
The instance number to be assigned to the device.
The name of the driver that the LUN and legacy hardware paths are to be bound to.
RETURN VALUE
Exit values are:
Successful completion.
An error condition occurred.
EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class.
Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number
Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot.
WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short
window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If
this happens, must be executed again to bind the desired driver.
may be executed only by the superuser.
SEE ALSO ioscan(1M), intro(7).
iobind(1M)