tpt
tpt (Trace Posix Threads)
=== ====== ===== ========
tpt collects data on the use of certain Posix threads functions
that can strongly impact application performance. This data
is stored in a per-thread binary output file whose size depends
on the number of times these functions are called during the
lifetime of the thread. These files should be stored in high
performance local file systems to minimize the impact of tpt
on the performance of the application. The information stored
in these files can then be summarized and reported by the
`tptrep' filter.
tpt is invoked as:
% tpt [-d] [-f] [-h] [-o pattern] [-q sig] command args...
where
-d
Tells tpt to start each thread with monitoring disabled.
See the libhistx documentation for information on the use of this feature.
-f
Tells tpt to produce a file for any processes fork()ed by the initial
process. This is off by default.
-h
Displays a brief help message. The command, if given, is not run.
-o <pattern>
Tells tpt to write it's per-thread data to a file with path given by
<pattern>. The default pattern is "tpt.%a.%t". Each pair
of the form %<char> in the pattern is expanded into the path as follows:
%a
Expands to the name of the application, e.g. "a.out"
%h
Expands to the value of the environment variable HOST
%i
Expands to the SN partition ID
%p
Expands to the process ID (PID)
%t
Expands to the thread ID (TID)
If a pattern is given that contains no %<char> pairs, it is replaced
with a pattern consisting of the original followed by ".%a.%t".
-q <sig>
Causes tpt to install a `quit' signal hander for signal <sig>.
When the `quit' signal is received, all threads will flush and close their
output files and cease all further monitoring activity. This is useful
when it is desired to kill a ling running application before it terminates
normally. <sig> can be a number, e.g. 10, or a kill(1) name, e.g. USR1.
NOTE: tpt does not work on statically linked applications.