On Jul 24, 2008, at 5:12 PM, Norberto Meijome wrote:
I'm interested in knowing the application level RTT for a HTTP
ie, not from SYN , SYN/ACK ... FIN , FIN/ACK , but from the POST
in wireshark) by an app on my side to the response by the server
(http.response). I have no access to either app's code.
Try something like this on the webserver or client machine:
# tcpdump -ttt -q -n -A tcp port 80
tcpdump: verbose output suppressed, use -v or -vv for full protocol
listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes
000000 IP 22.214.171.124.49729 > 126.96.36.199.80: tcp 488
9".,....GET /server-status HTTP/1.1
001348 IP 188.8.131.52.80 > 184.108.40.206.49729: tcp 1448
....9".,HTTP/1.1 200 OK
...which indicates a delay of 1.348 ms from the HTTP GET to the HTTP
200 response. This is using the following "delta timestamp" mode;
-ttt Print a delta (in micro-seconds) between current and
line on each dump line.)
If you use tcpdump -w to save the packets captured to a file for
analysis, you can feed it to net/tcpflow port to reconstruct this into
individual flows, which will make it easier to figure out if your
traffic starts getting interleaved.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"