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 SUSE
vfs_readahead
VFS_READAHEAD(8) System Administration tools VFS_READAHEAD(8)NAME
vfs_readahead - pre-load the kernel buffer cache
SYNOPSIS
vfs objects = readahead
DESCRIPTION
This VFS module is part of the samba(7) suite.
This vfs_readahead VFS module detects read requests at multiples of a given offset (hex 0x80000 by default) and then tells the kernel via
either the readahead system call (on Linux) or the posix_fadvise system call to pre-fetch this data into the buffer cache.
This module is useful for Windows Vista clients reading data using the Windows Explorer program, which asynchronously does multiple file
read requests at offset boundaries of 0x80000 bytes.
The offset multiple used is given by the readahead:offset option, which defaults to 0x80000.
The size of the disk read operations performed by vfs_readahead is determined by the readahead:length option. By default this is set to the
same value as the readahead:offset option and if not set explicitly will use the current value of readahead:offset.
This module is stackable.
OPTIONS
readahead:offset = BYTES
The offset multiple that causes readahead to be requested of the kernel buffer cache.
readahead:length = BYTES
The number of bytes requested to be read into the kernel buffer cache on each readahead call.
The following suffixes may be applied to BYTES:
o K - BYTES is a number of kilobytes
o M - BYTES is a number of megabytes
o G - BYTES is a number of gigabytes
EXAMPLES
[hypothetical]
vfs objects = readahead
VERSION
This man page is correct for version 3.0.25 of the Samba suite.
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
Samba 3.5 06/18/2010 VFS_READAHEAD(8)