🚀 go-pugleaf

hp@floor.uucp.risc.net (High Priest) writes:

> Well, I would be happy with 1000 cps. I'm currently getting 400-500 cps 
> on a v.32bis connect from my feed. (UNIX machine)

  1000 cps would be excellent for a v.32 feed, but not very good with a
v.32bis feed.

> The admin at my feed says there's nothing he can do, the 'g' protocol is 
> simply too inefficient. Is there anything that I can do?

  I get 1300+ cps with my v.32bis newsfeed and 970+ cps with my v.32
newsfeed.  This is on files of 50k or larger of 16-bit compressed news.
Your throughputs will be affected by several things including but not
limited to: the load on your host, the load on your system, the like
quality of your connection, serial drivers in use on both ends, locked com
port speed on both ends (some *NIX machines simply can't lock at higher
than 9600 Bps), capability of your CPU to sustain high throughput, your
fossil driver (I use X00 v1.49a in my DOS session here) and a host of
other things.

  I even get 1200+ cps on my L/D mail feed using v.32bis on larger files,
and I am running Waffle in an OS/2 DOS session using Ray Guinn's latest
SIO drivers (v0.40 just arrived here this morning).

> 450 cps on a 14,400 connect is pathetic.

  Agreed!

--
Internet: dalew@pdx.com                    P r a i s e   t h e   L o r d !
Home BBS: (503)335-9600 at 2400 - 9600 Bps using a 16.8k HST Dual Standard
          (503)335-3053 at 2400 - 14.4k Bps using an Intel 14.4EX
          Your friendly BlueWave and Waffle Beta/Distribution site