Re: Unnecessary Frame Fragmentation using beepcore-c?

Darren's suggestion about sending too fast and your suggestion about the
window size both sound promising.  The very first few frames were not
fragmented, but before long it began to fragment as I described, and I was
indeed feeding the frames in very rapidly.

So how does one adjust the window size, and what is a sensible amount to 
set it to?  This is currently running over loopback, where MTU is 16K.

Meanwhile I've modified my application to reassemble the tiny fragments as
needed, but I expect that avoiding the fragmentation in the first place
will substantially improve performance.

DCN

On Wed, 10 Sep 2003, William J. Mills wrote:
> This has to do with the frame size and window size.  The data payload
> will be reduced by the amount of the frame headers, which is the 
> missing info to make the payload sizes make more sense I think.
> 
> My suspicion is that the frame and window sizes are perhaps
> similar....  try cranking up the window size and see what that does.
> 
> -bill

-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf