Hello Tobias, > > Yes, I've tried that and got 12MB/s for standard Windows file copy > (CIFS), 4MB/s for FTP file copy using Internet Explorer and 3MB/s for > FTP file copy using the ICS demo client.
Strange, I can upload a big file at around 5,5 MB/sec using TFTPCli in a 100 MBit/s LAN, I think it could be even faster since the write cache is disabled on the server HDDs. > I have also tested these client using different round-trip-times (I > have > a GNU/Linux router in between in my test setup where I can adjust RTT) > and realized that they degrade quite different when increasing the RTT > (2ms, 4ms) so I asked myself how to handle this. Why do you want to increase the RTT when speed is what you are interested in? >> You may also write two very simple client and server applications. >> The client sending 256KB of data comming from memory (to avoid disk >> I/O slowness) and the server just reading the data and throwing it >> away (do not write to disk or allocate memory to store data). You'll >> have an idea abour the maximum thruput you can have. I just did a quick test with such a simple ICS client and server to achieve high transfer rates (all with default settings and a $FFFF bytes, custom send/receive buffer allocated once at application start). In a 100 MBit/s LAN I was able to send around 98 MBit/s, the average RTT was 0.7 ms (Wireshark). But I wonder why a single call to Receive() returns far more bytes than the per-socket kernel buffer space reserved for receives (I got up to $FFFF bytes in a single call)? Looks like winsock.dll buffers incomming data as well. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
