Hi Wilfried, > You find on my site a few programs to test performance with TWSocket.
I have found the PerformanceTest project and tested it. In the first run it also gave the well-known value of ~1.2MB/s. Then I digged into TWSocket's Send() function and found the BufSize property. After changing the BufSize to 1MB (I have read the warning about setting it larger than SocketSndBufSize in the comments but wanted to try myself) I got rates of ~7.7MB/s - what an improvement! Looks like http://support.microsoft.com/default.aspx?scid=kb;en-us;823764 is wrong in my special case or the system is automagically increasing the socket's send buffer behind the scenes. When I read the socket send buffer size with getsockopt() while the transfer is running it remains at 8192 bytes, though. So shall I explicitly add a call setsockopt() that increases the socket send buffer dramatically (>1MB)? What is your opinion about that? /Tobias -- NOA Audio Solutions Vertriebsges.m.b.H. Tel: +43-1-5452700 Johannagasse 42/4 Fax: +43-1-545270014 A - 1050 Wien Www: http://www.noa-audio.com -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
