05-03-2013
How to measure waiting time in run queue?
Hello guys,
I am doing a performance analysis on one of our psystem. Most of time I am using Nmon analyser to do my trend graph. But I can't find any help with it. We are interesting in the time spend by tasks in Aix run queue.
After looking the Aix documentation, I am pessimist to find any straight metric in order to measure that time.
So I need your help
Regards
Tech infos : Aix 6.1.6 on Power7
9 More Discussions You Might Find Interesting
1. HP-UX
Gurus,
Having a GS1280 box with OSF1 v5.1 installed (16 processors), the run queue value from the vmstat command reports a very high value (about 25 to 30). Does this reflect a CPU bound system. Note that the average CPU utilization is about 60 % which means that the CPU is not that loaded.
Can... (0 Replies)
Discussion started by: Negm
0 Replies
2. AIX
Hi all,
I am trying to find out the process wait time on Unix(AIX/SOLARIS) machine( only sh/ksh/csh):
Like
EXAMPLE 1 :
$ vmstat 2
System configuration: lcpu=16 mem=32000MB
kthr memory page faults cpu
----- -----------... (4 Replies)
Discussion started by: chandrakala.sg
4 Replies
3. UNIX for Dummies Questions & Answers
Im using the vmstat command to display the CPU run queue, but i want to put that into a program so is there a way to just display the number under the r?
Thanks, (1 Reply)
Discussion started by: RAFC_99
1 Replies
4. UNIX for Advanced & Expert Users
I am working on an application with some rather interesting build performance issues. If we build on Solaris/Linux x86/AMD64 the build is rather fast, but it takes more than five times as long on our Solaris Sparc servers (single-threaded builds on the workstations, but multi-threaded on the... (5 Replies)
Discussion started by: Elric of Grans
5 Replies
5. Shell Programming and Scripting
I have no idea why this job has been put into waiting state by server. Can anyone help me to run this job from waiting state.
ps -elf | grep 'usr_script'
4 S usr_script 3929 3926 0 77 0 - 2976 wait Oct21 ? 00:00:00 /bin/ksh /application_folder/script/report
0 S usr_script ... (2 Replies)
Discussion started by: zooby
2 Replies
6. Linux
Hi,
Am doing an enhancements related to monitoring a Linux disk I/O statistics.
The /proc/diskstats file is used to get the each disk I/O statistics. But, It returns the raw value.
How to calculate the Disk Queue Length and Disk Busy time from the raw values.
Guide me. (1 Reply)
Discussion started by: maruthu
1 Replies
7. Shell Programming and Scripting
Hello,
I am running GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu). I have a specific question pertaining to waiting on jobs run in sub-shells, based on the max number of parallel processes I want to allow, and then wait... (1 Reply)
Discussion started by: srao
1 Replies
8. UNIX for Advanced & Expert Users
Hi Everybody,
Can anybody explain how CPU idle% is about 50%, but runq-sz more than 1?
sar from Solaris 10:
00:00:05 %usr %sys %wio %idle
17:00:08 27 12 0 61
17:20:05 40 15 0 45
17:40:05 27 12 0 61
18:00:05 23... (2 Replies)
Discussion started by: sant
2 Replies
9. Solaris
Hi
I have a system running solaris 10, and I intend to use a NetApp as its storage system. The application requires a throughput between the server and the storage 7000 disk IOPS (random IO sustained throughput with response time of 20 mili second and 16k block size).
How to make sure that I... (6 Replies)
Discussion started by: fretagi
6 Replies
LEARN ABOUT DEBIAN
go-testflag
GO-TESTFLAG(7) Miscellaneous Information Manual GO-TESTFLAG(7)
NAME
go - tool for managing Go source code
DESCRIPTION
The 'go test' command takes both flags that apply to 'go test' itself and flags that apply to the resulting test binary.
The test binary, called pkg.test, where pkg is the name of the directory containing the package sources, has its own flags:
-test.v
Verbose output: log all tests as they are run.
-test.run pattern
Run only those tests and examples matching the regular expression.
-test.bench pattern
Run benchmarks matching the regular expression. By default, no benchmarks run.
-test.cpuprofile cpu.out
Write a CPU profile to the specified file before exiting.
-test.memprofile mem.out
Write a memory profile to the specified file when all tests are complete.
-test.memprofilerate n
Enable more precise (and expensive) memory profiles by setting runtime.MemProfileRate. See 'godoc runtime MemProfileRate'. To pro-
file all memory allocations, use -test.memprofilerate=1 and set the environment variable GOGC=off to disable the garbage collector,
provided the test can run in the available memory without garbage collection.
-test.parallel n
Allow parallel execution of test functions that call t.Parallel. The value of this flag is the maximum number of tests to run
simultaneously; by default, it is set to the value of GOMAXPROCS.
-test.short
Tell long-running tests to shorten their run time. It is off by default but set during all.bash so that installing the Go tree can
run a sanity check but not spend time running exhaustive tests.
-test.timeout t
If a test runs longer than t, panic.
-test.benchtime n
Run enough iterations of each benchmark to take n seconds. The default is 1 second.
-test.cpu 1,2,4
Specify a list of GOMAXPROCS values for which the tests or benchmarks should be executed. The default is the current value of
GOMAXPROCS.
For convenience, each of these -test.X flags of the test binary is also available as the flag -X in 'go test' itself. Flags not listed
here are passed through unaltered. For instance, the command
go test -x -v -cpuprofile=prof.out -dir=testdata -update
will compile the test binary and then run it as
pkg.test -test.v -test.cpuprofile=prof.out -dir=testdata -update
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-TESTFLAG(7)