09-02-2011
The default was engineered for low-latency networks, I thought, hence the emphasis on engineering better algorithms for higher latency.
7 More Discussions You Might Find Interesting
1. IP Networking
I have a Cisco small business switch and I am wondering what I will gain (or lose) by enabling "TCP congestion avoidance". I read the definition of it but how does one know when one should use it? (0 Replies)
Discussion started by: herot
0 Replies
2. IP Networking
I have noticed that the initial congestion window in my traces is 8920bytes~=6*1448. rfc3390 states the initial cwand should be max 4000 bytes(around 3*1448).
At first i thought it might be because i'm running my server on mac os x, so apple might have modified the tcp stack. Therefore I tried... (2 Replies)
Discussion started by: ddayan
2 Replies
3. AIX
Hello All
I have a system running AIX 61 shared uncapped partition (with 11 physical processors, 24 Virtual 72GB of Memory) .
The output from NMON, vmstat show a high run queue (60+) for continous periods of time intervals, but NO paging, relatively low I/o (6000) , CPU % is 40, Low network.... (9 Replies)
Discussion started by: IL-Malti
9 Replies
4. Solaris
I have a client with a meshed Cisco backbone.
6500's on top, Nexus 7000 in the middle and 4500's in bottom.
Solaris 10 servers connected to the 4500's backing up to a RedHat Linux backup server connected to the Nexus 7000's. The traffic is routed from 4500 --> Nexus 7000 --> 6500 --> Nexus 7000... (3 Replies)
Discussion started by: crusoe
3 Replies
5. AIX
Hi every one,
we have a set up in solaris 8 and 9 and running many cshell scripts.. we are migrate to AIX . Now, i want to know the latency difference between two boxes(Solaris and AIX). Kindly help me to , how to do Latency test.. (0 Replies)
Discussion started by: Madhu Siddula
0 Replies
6. Solaris
Hi every one,
we have a set up in solaris 8 and 9 and running many cshell scripts.. we are migrate to AIX . Now, i want to know the latency difference between two boxes(Solaris and AIX). Kindly help me to , how to do Latency test.. (2 Replies)
Discussion started by: Madhu Siddula
2 Replies
7. Solaris
I have problem with oracle solaris 10 running on oracle sparc T4-2 server.
Os information: 5.10 Generic_150400-03 sun4v sparc sun4v
Output from tcpstat.d script
TCP bytes: out outRetrans in inDup inUnorder
6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies
LEARN ABOUT OPENDARWIN
latency
LATENCY(1) BSD General Commands Manual LATENCY(1)
NAME
latency -- monitors scheduling and interrupt latency
SYNOPSIS
latency [-rt] [-c codefile] [-l logfile] [-st threshold] [-it threshold] [-s sleep_in_usecs] [-d decrementer_in_usecs] [-n kernel]
DESCRIPTION
The latency utility provides scheduling and interrupt latency statistics. It requires root privileges due to the kernel tracing facility it
uses to operate.
The arguments are as follows:
-rt Set real time scheduling policy. Default policy is timeshare.
-c When the -c option is specified, it takes a path to a codefile that contains the mappings for the system calls. This option over-
rides the default location of the system call codefile which is found in /usr/share/misc/trace.codes.
-l Specifies a logfile that is written to when either the interrupt or scheduling latency is exceeded.
-st Set the scheduler latency threshold in microseconds. If latency exceeds this, and a logfile has been specified, a record of what
occurred during this time is recorded.
-it Set the interrupt latency threshold in microseconds. If latency exceeds this, and a logfile has been specified, a record of what
occurred during this time is recorded.
-s The -s option sets the timer. It takes microseconds as an argument, the default timer is set to 1000 microseconds.
-d The -d option sets the decrementer. It takes microseconds as an argument. The decrementer is set back to the system default on
exit.
-n By default, latency acts on the default /mach_kernel. This option allows you to specify an alternate booted kernel.
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 -rt -st 20000 -it 1000 -l /var/tmp/latency.log
The latency utility will set the realtime scheduling policy. The threshold for the scheduler is set to 20000 microseconds. The threshold
for interrupts is set to 1000 microseconds. Latencies that exceed these thresholds will be logged in /var/tmp/latency.log.
SEE ALSO
top(1), fs_usage(1), sc_usage(1)
Mac OS X March 28, 2000 Mac OS X