Date: Mon, 18 Nov 1996 11:01:07 -0500 From: dennis@etinc.com (dennis) To: Joe Greco <jgreco@brasil.moneng.mei.com> Cc: isp@freebsd.org Subject: Re: changed to: Frac T3? Message-ID: <199611181601.LAA28913@etinc.com>
next in thread | raw e-mail | index | archive | help
>> J. Greco writes... >> >> >> >No, I have a bad habit of routing on low end equipment... >> > >> >But I agree... if a P100 can do 5000pps, what can a PP200 do :-) >> >> Perhaps if Joe would describe this test it would be a good start. > >I did, briefly, already. > >System: ASUS P/I-P55T2P4, P100 CPU, 16MB RAM, Znyx 314 quad DE21040 > ethernet, NE2000 ethernet. Well...a verbal description of what you were doing was what I was looking for..... flood pings are a pretty stinky test....the goal is to find out what it can switch on a continuous basis without packet loss...you may be chugging along at 10,000pps and someone pings the machine and you drop a flurry of packets while the ping is being processed, which is clearly unacceptable. its also a bit different with lots of different addresses being looked up (rather than the same one with a ping).....its pretty difficult to test. at 350 >> Anyone have a feel for the avg packet size over a typical backbone >> link? A T3 with an avg packet size of 500 bytes is 21000pps full >> duplex...I suspect the ave packet size may be smaller with lots >> of dialup traffic..... > >I tend to see an average of about 350 bytes. ok, thats about 28,000pps (allowing for overhead)...14,000 in one direction with a full pipe. Dennis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611181601.LAA28913>