Hello Arno,
> I would play with sligtly increased SocketSndBufSize and a BufSize set
> to something below like 16/8 and 32/16 kb. TWSocket's property
> BufSize actually is the block size and the amount of data copied into
> the winsock buffer in a single (winsock) send call.
Unfortunately the co
Tobias Rapp wrote:
> Hello Arno,
>
>>> By default winsock's send buffer size is 8 kb which is much bigger
>>> than TFtpCli's constant BLOCK_SIZE of 1460 bytes. So one condition
>>> described in the article is not true since a single send call in
>>> TFtpCli does not fill the whole underlying winso
Hello Arno,
>> By default winsock's send buffer size is 8 kb which is much bigger
>> than TFtpCli's constant BLOCK_SIZE of 1460 bytes. So one condition
>> described in the article is not true since a single send call in
>> TFtpCli does not fill the whole underlying winsock send buffer.
>> I realy
Arno Garrels wrote:
> Tobias Rapp wrote:
>
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;823764
>
> By default winsock's send buffer size is 8 kb which is much bigger
> than TFtpCli's constant BLOCK_SIZE of 1460 bytes. So one condition
> described in the article is not true since a s
Tobias Rapp wrote:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823764
By default winsock's send buffer size is 8 kb which is much bigger
than TFtpCli's constant BLOCK_SIZE of 1460 bytes. So one condition
described in the article is not true since a single send call in
TFtpCli does n
Hello Wilfried,
>> 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
>
> Can you resent the URL please ? It seems dead here.
http://support.microsoft.com/default.aspx?scid=kb;en-us;823764
It'
Hello Tobias,
> 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
Can you resent the URL please ? It seems dead here.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.htm
Hi SZ,
> 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 expla
wikipedia.
Regards,
SZ
- Original Message -
From: "Tobias Rapp" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, January 16, 2007 2:56 PM
Subject: Re: [twsocket] Throughput problem with TWSocket over a "long line"
> Hi SZ,
>
>> I
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
Tuesday, January 16, 2007 12:16 PM
Subject: Re: [twsocket] Throughput problem with TWSocket over a "long line"
> 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 fir
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
Hello Tobias,
You find on my site a few programs to test performance with TWSocket.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Monday, January 15, 2007, 16:33, Tobias Rapp wrote:
>> To improve performance you can make your packets equal
> To improve performance you can make your packets equal to the MTU, or
> switch Nagle off. There are some notes on Microsoft site about this. If
> you search for Nagle on MSDN you will find a lots information about
> that. They dont encourage to switch it off but in some cases (maybe
> yours) it i
Hello Tobias,
> TCP/IP connection with high round trip times and small packet sizes
If packets are < max MCU then Nagle will come in and will wait a while
to see if you want to send a packet again. Nagle does this to try to
concat packets to a larger one to fit into the max packet size.
Specially
Hello Tobias,
Do you see any CPU overload server side during transfert ?
regards.
--
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
Hello Dod,
> Are you using ICS in sync or async mode ?
I'm using ICS in async (event driven) mode in my application. The file
is sent in fragments of 256KB in the OnDataSent event handler.
> Do yo use same buffer and write-to-disk as Indy ?
When comparing ICS and Indy I did not use my applicati
Hello Tobias,
Are you using ICS in sync or async mode ?
Do yo use same buffer and write-to-disk as Indy ?
Do you use multi-threading or not ?
Is it binary or text file (I guess it is text file as you said "long
line" in the subject ?
Regards.
TR> I have a throughput/performance problem usin
18 matches
Mail list logo
