[net-perf] impact of testing on other services?

Mike Iglesias iglesias at draco.acs.uci.edu
Tue Jun 28 13:36:34 PDT 2005


> However, I thought I would present a perhaps-interesting result.  I
> started pinging the UCSC webserver from my office workstation.  I then
> scheduled a bwctl test between our bwctl server and UCSC's bwctl
> server. Our bwctl server is not the same machine as my workstation,
> and I assume that UCSC isn't running its bwctl server on its main
> website.  You can clearly see the jump in latency during the 10-second
> bwctl test:

I ran a similar test from UCI to UCLA, while pinging the UCLA web
server.  Not much of a change there during the test.

PING www.ucla.edu (169.232.56.135) 56(84) bytes of data.
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=0 ttl=56 time=7.32 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=1 ttl=56 time=7.17 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=2 ttl=56 time=7.17 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=3 ttl=56 time=7.10 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=4 ttl=56 time=7.17 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=5 ttl=56 time=7.13 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=6 ttl=56 time=7.14 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=7 ttl=56 time=7.11 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=8 ttl=56 time=7.14 ms
[ I think the test started here ]
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=9 ttl=56 time=7.27 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=10 ttl=56 time=7.25 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=11 ttl=56 time=7.18 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=12 ttl=56 time=8.15 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=13 ttl=56 time=7.46 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=14 ttl=56 time=7.24 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=15 ttl=56 time=7.42 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=16 ttl=56 time=7.57 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=17 ttl=56 time=7.18 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=18 ttl=56 time=7.39 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=19 ttl=56 time=7.16 ms
[ ended here ]
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=20 ttl=56 time=7.17 ms
64 bytes from www.ucla.edu (169.232.56.135): icmp_seq=21 ttl=56 time=7.10 ms


bwctl output:
$ bwctl -c bwctl-egw.nac.uci.edu -s bwctl-1.border.ucla.net -A A AESKEY uci -w 2m -t 10
Enter passphrase for identity 'uci':
bwctl: 18 seconds until test results available
RECEIVER START
3328979555.146336: /usr/local/bin/iperf -B 128.200.34.52 -P 1 -s -f b -m -p 5004 -w 2097152 -t 10
------------------------------------------------------------
Server listening on TCP port 5004
Binding to local address 128.200.34.52
TCP window size: 4194304 Byte (WARNING: requested 2097152 Byte)
------------------------------------------------------------
[ 14] local 128.200.34.52 port 5004 connected with 169.232.34.34 port 5004
[ ID] Interval       Transfer     Bandwidth
[ 14]  0.0-10.0 sec  861143040 Bytes  686964757 bits/sec
[ 14] MSS size 1368 bytes (MTU 1408 bytes, unknown interface)
[ 14] Read lengths occurring in more than 5% of reads:
[ 14]  1368 bytes read 380514 times (86.2%)
[ 14]  8192 bytes read 28068 times (6.36%)
RECEIVER END


Mike


More information about the Network-performance mailing list