Re: silly windows

On Tue, 30 Mar 2004, William J. Mills wrote:
> I am trying to implement the spirit of "Nagle's algorithm" here,
> one part of which is not to send more than one tiny frame in
> sequence.  The major difference is that it applies to TCP and
> uses the concepts of MSS and window size, and we don't have MSS
> in BEEP.
> 
> I compiles and ran (with c-> rather than b-> as you note) last
> night, using beepng.  WIth window size of 4K and sending 4K
> payloads you do still end up with tiny frames sent, but they
> are much less frequent.  With the restriction of opening the 
> window at least 50% it's rediced the silliness a lot already right?
> Sending a small frame that completes the message is not "silly"
> 
> Thoughts?

It may be avoiding some of the REALLY silly windows like 100 byte 
fragments of a 4K frame.  But at apparent_out_window/4, it can break a 4K 
frame up into 4 framelets, and frequently breaks one up into 2 or 3.

What would happen if I refused to accept anything less than 
c->commit_frame->size?  Would that cause a stall of some sort?

I note that c->apparent_out_window is only 4K, despite seemingly having
set the window size to be 64K at both ends using bpc_set_channel_window()
in pro_start_indication() and my _start()  function.  Am I setting the
wrong thing, or in the wrong places?

BTW, I only have one active channel right now, so various algorithms for 
choosing the channel won't make much difference except to the extent they 
disqualify our only channel from sending at the moment.

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



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click