Sponsored Content
Top Forums UNIX for Advanced & Expert Users Redhat - IO performance measurement Post 302893268 by jim mcnamara on Tuesday 18th of March 2014 08:34:34 AM
Old 03-18-2014
dtrace does not work on Redhat - try systemtap. https://sourceware.org/systemtap/wiki/HomePage

That is a good tool. It requires some learning, and is able to probe directly into processes and driver information. However, that is what some existing tools do for you now.

But before you abandon iostat do not sell it short - iostat does provide good information.
You need to exploit some of the options.

sar -d (requires sa to be turned on, usually via crontab) does show great information.

vmstat -d does something similar. Very useful.

So, now that you see there are lots of tools, please show us a sample of your iostat output and your iostat command.
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Performance measurement of Code

I hope I am posting the query at right place.. I have the project running as 32 bit application on Solaris 8. I want to port this to 64Bit application. Before I start this process, I would like to compare the performance of a sample code running as 32Bit/64 Bit executables on a 64 bit... (1 Reply)
Discussion started by: amit_sapre
1 Replies

2. Programming

time measurement

I have a bottleneck in one of my applications...I have a loop that goes through a few thousand interations, but does quite a few things (digs info out of a database, sends the data to another application, etc...). I want to put in some debugging to determine what function calls are taking the most... (8 Replies)
Discussion started by: jalburger
8 Replies

3. UNIX for Dummies Questions & Answers

Commands performance measurement

Hi, Actually i wanted to check out the process time for the execution of commands on unix, i looking for the script which can include all commands which are to be executed on the system and i need to get the time for executing each command, can somebody help me Thanks & Regards Murali (1 Reply)
Discussion started by: hsmuralidhara
1 Replies

4. Shell Programming and Scripting

convert file storage size from one unit of measurement to another

The source number is always in megabytes and I need a script to covert into either MB,GB or TB displayed in a specific format. Source number examples: 5345376635 34255 5453645846353 The result has to be maximum 2 numbers after the comma 1.13 TB 134.17 TB 413.46 GB 678.45 MB I... (3 Replies)
Discussion started by: TehOne
3 Replies

5. IP Networking

SNMP OID for Network Utilization measurement

Hi everyone, I've just copied a snmpget script from somewhere. This script is basically used to collect basic router information. Ex: syscontact,syslocation,etc. And I want to extend the script to be able to collect some network information and utilization of some machines ex: bandwith usage,... (0 Replies)
Discussion started by: franzramadhan
0 Replies

6. Shell Programming and Scripting

Measurement file parsing

I have an application performance measurement file with one thousand lines. Each line has some text indicating type of measurement and the last field containing the measured value. Each of the file has a unique measurement. I am interested in only extracting about 100 of those measurements and put... (2 Replies)
Discussion started by: yoda9691
2 Replies

7. IP Networking

OID for Bandwith and Throughput Measurement

Hey Guys, Does anybody know, which OID's of Net-SNMP is used to collect throughput and bandwith usage of machine?? I got these OID's ..iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifOutOctets ..1.3.6.1.2.1.2.2.1.16 ... (1 Reply)
Discussion started by: franzramadhan
1 Replies
DTRACE(1)						      General Commands Manual							 DTRACE(1)

NAME
dtrace - Dtrace compatibile user application static probe generation tool. SYNOPSIS
dtrace -s file [OPTIONS] DESCRIPTION
The dtrace command converts probe descriptions defined in file.d into a probe header file via the -h option or a probe description file via the -G option. OPTIONS
-h generate a systemtap header file. -G generate a systemtap probe definition object file. -o file is the name of the output file. If the -G option is given then the output file will be called file.o; if the -h option is given then the output file will be called file.h. -C run the cpp preprocessor on the input file when the -h option is given. -I file give this include path to cpp when the -C option is given. -k keep temporary files, for example the C language source for the -G option. --types generate probe argument typedef information when the -h option is given. EXAMPLES
Systemtap is source compatible with dtrace user application static probe support. Given a file test.d containing: provider sdt_probes { probe test_0 (int type); probe test_1 (struct astruct node); }; struct astruct {int a; int b;}; Then the command "dtrace -s test.d -G" will create the probe definition file test.o and the command "dtrace -s test.d -h" will create the probe header file test.h Subsequently the application can define probes using #include "test.h" ... struct astruct s; ... SDT_PROBES_TEST_0(value); ... SDT_PROBES_TEST_1(s); The application is linked with "test.o" when it is built. SEE ALSO
stap(1) stappaths(7) DTRACE(1)
All times are GMT -4. The time now is 01:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy