Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

latency(1) [osx man page]

LATENCY(1)						    BSD General Commands Manual 						LATENCY(1)

NAME
latency -- monitors scheduling and interrupt latency SYNOPSIS
latency [-p] [-h] [-m] [-st threshold] [-it threshold] [-c code_file] [-l log_file] [-R raw_file] [-n kernel] DESCRIPTION
The latency utility provides scheduling and interrupt-latency statistics. Due to the kernel tracing facility it uses to operate, the command requires root privileges. The arguments are as follows: -c code_file When the -c option is specified, it takes a path to a code file that contains the mappings for the system calls. This option over- rides the default location of the system call code file, which is found in /usr/share/misc/trace.codes. -h Display high resolution interrupt latencies and write them to latencies.csv (truncate existing file) upon exit. -m Display per-CPU interrupt latency statistics. -it threshold Set the interrupt latency threshold, expressed in microseconds. If the latency exceeds this value, and a log file has been speci- fied, a record of what occurred during this time is recorded. -l log_file Specifies a log file that is written to when either the interrupt or scheduling latency is exceeded. -n kernel By default, latency acts on the default /mach_kernel. This option allows you to specify an alternate booted kernel. -p priority Specifies the priority level to observe scheduler latencies for. -st threshold Set the scheduler latency threshold in microseconds. If latency exceeds this, and a log file has been specified, a record of what occurred during this time is recorded. -R raw_file Specifies a raw trace file to use as input. The data columns displayed are as follows: SCHEDULER The number of context switches that fall within the described delay. INTERRUPTS The number of interrupts that fall within the described delay. The latency utility is also SIGWINCH savvy, so adjusting your window geometry will change the list of delay values displayed. SAMPLE USAGE
latency -p 97 -st 20000 -it 1000 -l /var/tmp/latency.log The latency utility will watch threads with priority 97 for scheduling latencies. The threshold for the scheduler is set to 20000 microsec- onds. The threshold for interrupts is set to 1000 microseconds. Latencies that exceed these thresholds will be logged in /var/tmp/latency.log. SEE ALSO
fs_usage(1), sc_usage(1), top(1) Mac OS X March 28, 2000 Mac OS X

Check Out this Related Man Page

2004-04-16

      mailping

      0.0.4

MAILPING-LATENCY(1)						     Mailping						       MAILPING-LATENCY(1)

NAME
mailping-latency - Munin plugin to graph latency of mail deliveries SYNOPSIS
/usr/share/mailping/munin-plugins/mailping-latency {[config] | ['']} DESCRIPTION
mailping-latency is a Munin plugin that monitors the time spent between email submit and it's delivery. Configuration output When passed config, it outputs Munin configuration information. If there are no circuits defined (no subdirectories in /etc/mailping), it specifies that Munin should draw no graph either. If configuration files /etc/mailping/circuit/warnlatency and /etc/mailping/circuit/faillatency exist, the values in them are passed on to Munin, for use in Nagios alert integration. Value output When passed an empty string '', mailping-latency outputs latency of last successful probe message, for each configured circuit. FILES
/etc/mailping/ List of circuits that exist; each subdirectory is a circuit. /etc/mailping/circuit/warnlatency If latency is greater than this many seconds, a Nagios warning is triggered by Munin (assuming it has been configured to do that). Default: no warnings. /etc/mailping/circuit/faillatency If latency is greater than this many seconds, a Nagios alert is triggered by Munin (assuming it has been configured to do that). Default: no alerts. /var/lib/mailping/state/circuit/latency Amount of latency in seconds of the last successful probe for circuit. ENVIRONMENT
MAILPING_CONFIGDIR Override the location of the configuration directory. Default: /etc/mailping MAILPING_STATEDIR Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories named after the circuit name. Default: /var/lib/mailping SEE ALSO
mailping-success(1), mailping-cron(1), mailping-store(1), munin-run(8), munin-node(8) AUTHOR
Tommi Virtanen <tv@havoc.fi> Havoc Consulting Author. COPYRIGHT
Copyright (C) 2004 Havoc Consulting mailping 0. 2004-04-16 MAILPING-LATENCY(1)
Man Page

Featured Tech Videos