Ok I think the problem is in sliding windows then. Make sure the receiving client/server has a large sliding window. There is a way to calculate it but I am not sure of the exact formula. Something related with the round trip times and bandwidth. Sliding windows _should_ be explained in wikipedia.
Regards, SZ ----- Original Message ----- From: "Tobias Rapp" <[EMAIL PROTECTED]> To: "ICS support mailing" <[email protected]> Sent: Tuesday, January 16, 2007 2:56 PM Subject: Re: [twsocket] Throughput problem with TWSocket over a "long line" > Hi SZ, > >> I think your problem should be in the message pump. What do you use >> for that in your thread? When I switched to GetMessage from >> PeekMessage, I was WOW! > > I use TWSocket's MessageLoop() function in my threaded application which > uses GetMessage() internally. And Wilfried's test programm uses no > threads at all. > > But the basic thing was not that I cannot reach more throughput than > 1.2MB/s at all. If I use two computers in my intranet I easily gain a > throughput of more than 20MB/s (disc IO included). It was a special case > that I had a problem with: When TCP/IP connection is going through an > ATM line (high round trip times). > > /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 -- 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
