🚀 go-pugleaf

Quoted from <...unknown> by ziegast@uunet.uu.net (Eric Ziegast):

> One of our subscribers was using a V.32/V.42/V.42bis connection at g(64,3)
> (that is, a packet segment size of 64 and a window size of 3) and seeing
> lousy throughput.  I asked him to try g(256,7) to g(1024,7).  He says that
> g(512,7) worked best.  Here are his stats for file transfers 8K and over
> for the past few days...
> 
> 	 Date-Time    (Sent+Recv)      Amount           Time        Avg Rate
> 	---------------------------------------------------------------------
> 	08/28-22:09   (   6+    )     1154247 bytes  1251.61 sec    922 cps
> 	08/29-05:07   (   4+    )      506719 bytes   531.55 sec    953 cps
> 	08/29-11:03   (   3+    )      185686 bytes   198.88 sec    933 cps
> 	08/29-14:17   (   1+    )       97965 bytes   105.70 sec    926 cps
> 	08/29-17:03   (   2+    )      153502 bytes   163.84 sec    936 cps
> 	08/30-00:19   (   1+    )     1045712 bytes  1107.31 sec    944 cps
> 	08/30-00:42   (   1+    )     1045712 bytes  1142.82 sec    915 cps
> 	08/30-16:54   (   1+    )       18220 bytes    17.88 sec   1019 cps
> 	08/30-18:07   (   2+    )      271854 bytes   346.72 sec    784 cps
> 	08/30-18:51   (   1+    )       42454 bytes    58.04 sec    731 cps
> 	08/30-21:28   (   3+    )      443635 bytes   486.98 sec    910 cps
> 	08/31-01:20   (   3+    )      407653 bytes   432.76 sec    941 cps
> 	08/31-05:02   (  15+    )      656011 bytes   696.09 sec    942 cps
> 	08/31-11:03   (   1+    )       19410 bytes    26.44 sec    734 cps
> 	08/31-23:06   (   7+    )     1301900 bytes  1385.17 sec    939 cps
> 	09/01-05:07   (   6+    )      817513 bytes   878.01 sec    931 cps
> 	09/01-23:07   (   8+    )     1678814 bytes  1830.68 sec    917 cps
> 	09/02-05:06   (   5+    )      546887 bytes   673.86 sec    811 cps
> 	09/02-23:05   (   8+    )     1439804 bytes  1509.72 sec    953 cps
> 	09/03-05:06   (   4+    )      541214 bytes   605.74 sec    893 cps
> 	09/03-23:06   (   8+    )     1557084 bytes  1648.31 sec    944 cps
> 	09/04-05:10   (   5+    )      748093 bytes   795.35 sec    940 cps
> 	Total:        (  95+    )    14680089 bytes 15893.46 sec    923 cps
> 
> 
> 	 Date-Time    (Sent+Recv)      Amount           Time        Avg Rate
> 	---------------------------------------------------------------------
> 	08/30-21:19   (    +   1)      120391 bytes   298.34 sec    403 cps
> 	09/02-05:03   (    +   1)       10844 bytes    21.57 sec    502 cps
> 	09/03-11:06   (    +   1)      121327 bytes   268.65 sec    451 cps
> 	09/04-05:05   (    +   1)       26524 bytes    53.36 sec    497 cps
> 	Total:        (    +   4)      279086 bytes   641.92 sec    434 cps
> 
> I don't know about the receive rate, but the sent rate looks awfully nice
> (especially since he downloads lot's of news from us).  It probably could
> be a little bit better though; I just realized I was still using level 7
> debugging on his line.  (Just turned it off.)
> 
> So, if you use Compuserve's 9600 connection and receive alot of files from
> uunet,
> 	- Try a higher packet segment and window sizes (like 512 and 7).
> 	- Turn on V.42 and V.42bis if you want.  Don't use MNP.
> 	- AND send mail to uunet!postmaster asking us to change the packet
> 	  settings on our end to match yours.
> 
> If your UUCP does not support larger packet sizes, consider using a newer
> UUCP implementation (like Taylor's).
> 
> Disclaimer: You milage will vary. ;^)
> --
> Eric Ziegast

	The above stats are mine, no need to keep my identity in the dark.
:-)  The Modem I am using to connect to Compuserve is a SupraFax 14400
modem.  The Line I connect to here in Miami is a 9600 Baud Compuserve
line.  I was getting some real lousy throughput and started to mess with
my settings.  I found that a Window of 7 and Segment of 512 is best on
Compuserve dialins.  One possoible explination as to why 512 is best was
given to me by some folks in the ALT.SYS.AMIGA.UUCP newsgroup.  I was
told that if I had a file waiting for transmital to UUNET and it was only
64 bytes, a full 512 size packet would still be sent.  The higher the
segment size the more time you waste in sending those small command files
and the like.  The explination at the time made sense.  Other more
enlightend soles guide me strait.  I tried other sizes from 1024 to 2048.
The throughput did slow as the segment size increased from 512.  The
reason the average throughput to UUNET is at 400 is that I send very
little mail back to UUNET.  I send 22K average to UUNET and receive 1.5
Megs average from UUNET Daily.  

	Things I have enabled while connected to the Compuserve Dialin is
RTC/CTS handshaking enabled.  V.42Bis Enabled.  This means I have error
correction with Compression active.  I also set serial port to comunicate
with my modem at 38400 baud.  

	I was going to post this information earlier, local circumstances
prevented it.  If anyone has any questions feel free to ask me by either
posting here or by mail.  I will get your message either way.

Carlos

--

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%    __     %  UUCP:  overlord@megalith.miami.fl.us  % I Tried MS-DOS Once %
% __///     %  Fido:  1:135/92                       % But Didn't Inhale.  %
% \\//Amiga %  GEnie: C.Amezaga                      %        --D.Atkins-- %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

	I live in Miami, FL which is close to the Cutler Ridge and
Homestead areas.  If you wish to contact someone you have been unable to
reach because of Hurricane Andrew send E-mail to
postmaster@megalith.miami.fl.us and I will try my best to reach them for
you.  Folks out there who are able, please donate to the American Red Cross
in anyway you can.  They are running low in Funds and this Hurricane is
only further draining their resoources.  There are many people here who
are in need of many common items.  Thank you and God Bless.