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 NETBSD
eshconfig
ESHCONFIG(8) BSD System Manager's Manual ESHCONFIG(8)NAME
eshconfig -- configure Essential Communications' HIPPI network interface
SYNOPSIS
eshconfig [-estx] [-b bytes] [-c bytes] [-d filename] [-i usecs] [-m bytes] [-r bytes] [-u filename] [-w bytes] [interface]
DESCRIPTION
eshconfig is used to configure device-specific parameters and download new firmware to the Essential Communications RoadRunner-based HIPPI
network interface. The interface is very sensitive to the DMA performance characteristics of the host, and so requires careful tuning to
achieve reasonable performance. In addition, firmware is likely to change frequently, which necessitates a reasonably easy way to update
that firmware.
Available operands for eshconfig:
-b bytes
Adjust the burst size for read (by NIC of host memory) DMA.
-c bytes
Adjust the burst size for write (by NIC of host memory) DMA.
-d filename
Filename for file to download into NIC firmware. This must be a file in the standard Essential format, with :04 preceding every
line, and a tag line at the end indicating the characteristics of the firmware file.
-e Write data to EEPROM. Normally, setting tuning parameters will only persist until the system is rebooted. Setting this parameter
ensures that the changes will be written to EEPROM.
-i usecs
Interrupt delay in microseconds.
-m bytes
Minimum number of bytes to DMA in one direction (read or write) before allowing a DMA in the other direction. Tuning this prevents
one direction from dominating the flow of bytes, and artificially throttling the NIC.
-r bytes
Bytes before DMA starts for read (from host to NIC). This controls how soon the DMA is triggered; until this many bytes are
requested, the DMA will not begin.
-s Show statistics for the HIPPI NIC. Repeat the option to suppress non-zero statistics.
-t Show current tuning parameters on the host.
-u filename
Name of file to which the NIC firmware should be uploaded. Not currently supported.
-w bytes
Number of bytes required before write (from NIC to host) DMA is started. Until this many bytes are ready to be written, the DMA will
not start.
-x Reset the NIC. This is necessary for the HIPPI-FP support, as ifconfig(8) will no longer physically reset the NIC when the inter-
faces goes up and down.
Only the super-user may modify the configuration of a network interface.
DIAGNOSTICS
Messages indicating the specified interface does not exist or the user is not privileged and tried to alter an interface's configuration.
SEE ALSO esh(4), ifconfig(8)HISTORY
The eshconfig command first appeared in NetBSD 1.4.
BSD June 17, 2005 BSD