There doesn't seem to be a simple way of collecting TCP stats from the server OS.
So taking a slightly different track, I was thinking of reusing the display scrolling code as a packet generator and creating a plugin to test link capacity by varying scrolling rates [eventually to become part of the health plugin]. This will only work with graphics players as it relies on the relatively large size of each display frame [1290 bytes in the case of SB2/3] On a wired network I can sustain 4Mbps to an SB2 with no TCP queue build up using this method. Above ~5M there is some TCP congestion, probably due to the small tcp window used for the slimproto session. However the area of interest is below this so this is probably a reasonable approach. It also has side effect that network performance is visible.. Any thoughts? What link rates should it attempt to test at? I am thinking: 128k, 192k, 320k, 1M, 1.5M, 2M, 4M -- Triode ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=16832 _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/beta
