Performance Testing the 7000 series, part 2 of 3


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Performance Testing the 7000 series, part 2 of 3
# 1  
Old 07-02-2009
Performance Testing the 7000 series, part 2 of 3

In part 2 of this three-part blog, Brendan Gregg provides a tuning checklist for achieving maximum performance on the Sun Storage 7410, particularly for finding performance limits. This kind of tuning is used during product development, to drive systems as fast as possible to identify and solve bottlenecks.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. AIX

Performance testing on AIX

I'm doing performance testing for one application which works on AIX. But I don't know which performance parameters of memory need to be collected. Now, I just know very few: 1. page in 2. page out 3. fre They are all collected by "vmstat" command. I want to know, except for above... (2 Replies)
Discussion started by: adasong
2 Replies
Login or Register to Ask a Question
ELVTUNE(8)						      System Manager's Manual							ELVTUNE(8)

NAME
elvtune - I/O elevator tuner SYNOPSIS
elvtune [ -r r_lat ] [ -w w_lat ] [ -b b_max ] /dev/blkdev1 [ /dev/blkdev2 ... ] elvtune -h elvtune -v DESCRIPTION
elvtune allows to tune the I/O elevator per blockdevice queue basis. The tuning can be safely done at runtime. Tuning the elevator means being able to change disk performance and interactiveness. In the output of elvtune the address of the queue tuned will be shown and it can be considered as a queue ID. For example multiple partitions in the same harddisk will share the same queue and so tuning one partition will be like tuning the whole HD. OPTIONS
-r r_lat set the max latency that the I/O scheduler will provide on each read. -w w_lat set the max latency that the I/O scheduler will provide on each write. -b b_max max coalescing factor allowed on writes when there are reads pending in the queue. -h help. -v version. NOTE
Actually the only fields tunable are those relative to the IO scheduler. It's not possible to select a one-way or two-way elevator yet. For logical blockdevices like LVM the tuning has to be done on the physical devices. Tuning the queue of the LVM logical device is useless. RETURN VALUE
0 on success and 1 on failure. HISTORY
Ioctls for tuning elevator behaviour were added in Linux 2.3.99-pre1. AUTHORS
Andrea Arcangeli <andrea@suse.de> SuSE Version 1.0 14 March 2000 ELVTUNE(8)