Date: Sat, 12 Dec 1998 17:38:23 +0100 From: "Julian Stacey" <jhs@jhs.muc.de> To: Ignatios Souvatzis <is@jocelyn.rhein.de> Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: data throughput Message-ID: <199812121638.QAA02043@jhs.muc.de> In-Reply-To: Your message of "Fri, 11 Dec 1998 21:31:15 %2B0100." <19981211213115.B458@jocelyn.rhein.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Ignatios Souvatzis wrote: > On Thu, Dec 10, 1998 at 12:51:38AM +0100, Julian Stacey wrote: > > > while the ta offered a rate of 7.5kbps the fritzcard only > > > provided 7.0kbps. > > > > FYI I get about 7.85 K (from memory, ie just under 8) out of my ISP muc.de > > (all my mail incoming gets queued by uucp localy there, so it saturates the > > link bandwidth for optimal efficiency :-) > > Creatix 16 bit, i4b-00.63-alpha-100798 > > I just got: > > 100% |**************************************| 313 KB 7555 B/s 00:00 E I quoted raw link rate shown by /usr/local/bin/isdnd -f . It is not generally appropriate to consider a single ftp task rate when considering throughput of the isdn system because: - ftp data rate will not show data used in ftp protocol overhead. - any intermediate site on the ftp route, or, more likely, the source ftpd, (& discs etc) if experiencing a system load, may stop feeding you for a percentage of the time. Only uses I can think of in quoting an FTP rate are: - to compare with WindDOS PC single tasking [l]users ;-) - to initially verify if hm@'s code is aprox correct, & not off by some large factor (which it doesn't seem to be, but always good to verify assumptions, (Viz. old modems' "CONNECT rate" messages ) To see link max rate, it must be saturated, & unless you can guarantee your other end's behaviour, I suggest soak the link like I normally use mine: [ All mail incoming is queued by host other end of isdn link, waiting for me] : so trigger it to flow, + start a few web browsers pointing at URLs noted from mail, + start a few ftp fetches of new source .tgz 's you want, + start an rdist/rsync update of some remote directories + wait a while for process setup to occur, ... then look at what your completely saturated ISDN link is shifting. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812121638.QAA02043>