Good Stuff Happens in 1:1 Meetings: Why you need them and how to do them well
2012 09-28 09-52-48-netlog
1. Fri Sep 28 09:52:48 2012: LogOut_File: : logfile started
Fri Sep 28 09:52:48 2012: Net Status: low-level initialize success.
Fri Sep 28 09:52:48 2012: Note that this new version (12/19/2011) has reduced
the frequency of updates so the numbers will be larger
Fri Sep 28 09:52:48 2012: time = time of logging
Fri Sep 28 09:52:48 2012: address = address of IP address
Fri Sep 28 09:52:48 2012: incoming = total size of messages set to me in bytes.
Spikes can indicate lag.
Fri Sep 28 09:52:48 2012: outgoing = total size of messages set from me in
bytes. Spikes can indicate lag.
Fri Sep 28 09:52:48 2012: app_ctos = client to server bytes delta excluding
overheads (app data only)
Fri Sep 28 09:52:48 2012: app_stoc = server to client bytes delta excluding
overheads (app data only)
Fri Sep 28 09:52:48 2012: loss = number of packets lost. Can indicate lags.
Some node on the network is dropping packets or taking to long and we have to
resend them.
Fri Sep 28 09:52:48 2012: sent = number of packets sent. Spikes can indicate
lag.
Fri Sep 28 09:52:48 2012: ping = how long it takes for a packet to get back and
forth. Spikes can indicate lag.
Fri Sep 28 09:52:48 2012: variance = how much the ping is changing from avg
ping. Spikes can indicate lag.
Fri Sep 28 09:52:48 2012: reliable delayed = This occurs when we drop reliable
packets from sending this frame because we are sending to much data. Unreliable
are more likely to be dropped than reliable.
Fri Sep 28 09:52:48 2012: unreliable delayed = This occurs when we drop
unreliable packets from sending this frame because we are sending to much data.
Fri Sep 28 09:52:48 2012: app update delayed = This occurs when the app is
taking to long to run code caused by network packets (ie CPU) and packets are
delayed until the next frame
Fri Sep 28 09:52:48 2012: Time spent in critical section (frame) = This is the
time the network thread is blocking the main thread from doing anything.
Fri Sep 28 09:52:48 2012: [time], [address], [incoming], [outgoing], [app_ctos],
[app_stoc], [loss], [sent], [ping], [variance], [reliable delayed], [unreliable
delayed], [app update delayed], [Time spent in critical section (frame)]
Fri Sep 28 09:52:53 2012: A new client connected from 66.151.33.80.
5097,66.151.33.80,200,158,0,0,0,7,377,110,0,0,0,0
16068,66.151.33.80,6634,1141,5328,449,1,58,267,7,0,0,0,0
Fri Sep 28 09:53:06 2012: Network Thread stall for 83
Fri Sep 28 09:53:06 2012: Network Thread stall for 78
Fri Sep 28 09:53:09 2012: Network Thread stall for 73
Fri Sep 28 09:53:09 2012: Network Thread stall for 71
26245,66.151.33.80,22235,1600,3517,5,2,72,279,22,0,0,7,0
36257,66.151.33.80,36605,2384,24915,292,4,89,279,18,0,0,14,0
46260,66.151.33.80,40096,4044,1798,1088,4,104,267,7,0,0,14,0
56310,66.151.33.80,41758,5539,723,989,4,120,267,4,0,0,14,0
66385,66.151.33.80,45033,7712,1675,1389,4,135,267,4,0,0,14,0
Fri Sep 28 09:54:02 2012: Network Thread stall for 84
76406,66.151.33.80,47046,8214,1288,166,4,153,267,4,0,0,15,0
86502,66.151.33.80,48991,8672,1311,138,4,169,267,4,0,0,15,0
96569,66.151.33.80,50940,9115,1335,125,4,183,267,4,0,0,15,0
106589,66.151.33.80,53339,9567,1803,140,4,198,267,4,0,0,15,0
116626,66.151.33.80,56864,10056,2852,131,4,213,267,4,0,0,16,0
126676,66.151.33.80,58823,10497,1301,117,5,229,268,5,0,0,16,0
136749,66.151.33.80,61287,10950,1857,139,5,245,268,4,0,0,16,0
146817,66.151.33.80,62626,11413,743,171,5,264,267,4,0,0,16,0
156849,66.151.33.80,64736,11935,1429,182,6,282,267,6,0,0,16,0
166876,66.151.33.80,66119,12498,721,231,6,300,267,3,0,0,16,0
176932,66.151.33.80,67266,13337,405,465,6,319,267,4,0,0,16,0
186980,66.151.33.80,77588,14616,8975,625,6,334,266,4,0,0,17,0
197009,66.151.33.80,84558,15967,5664,721,6,350,266,4,0,0,17,0
207041,66.151.33.80,101633,19495,13339,1692,6,367,266,4,0,0,21,0
217051,66.151.33.80,124387,23283,18750,1620,7,384,267,5,0,0,21,0