Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request From: edward@math.ucla.edu (Edward Dergharapetian) Newsgroups: comp.sys.sun Subject: Re: How does traffic(1) figure out the load Keywords: Networks Message-ID: <8902280129.AA16616@julia.math.ucla.edu> Date: 9 Mar 89 18:51:00 GMT Sender: usenet@rice.edu Organization: Sun-Spots Lines: 30 Approved: Sun-Spots@rice.edu Original-Date: Mon, 27 Feb 89 17:29:14 PST X-Sun-Spots-Digest: Volume 7, Issue 191, message 2 of 13 Thanks to everyone who replied. Although some people had suggestions on how traffic(1) works, alot of people asked me to post a summary of the answers. Here is what I found after reading some of the replies and further digging into the code. I originally thought of "load" monitoring in traffic as being: (packet count/size being broadcast)/(packets that the ethernet can handle) As it turns out that is NOT what the "load" monitor in traffic does. What actually happens is that traffic measures the number of packets that were read off the ethernet during an interval. This is then divided by the time interval in question. Some scaling is performed (i.e.: what you see on the traffic screen is in bits/millisecond). So in essence traffic measures the average throughput of the system during a certain time interval. It cannot determine that the ethernet was flooded (i.e: %100 load), since it doesn't know how many packets the ethernet can handle (no assumption is made). I guess the term "load" might not be appropriate in this case. Some people were also inquiring about any batch-like programs that collect ethernet stats. A statistics collection program called nnstat is available via anonymous ftp from 'isi.edu'. It seems pretty usable; however, it too doesn't provide true load statistics. edward. Edward Dergharapetian (213) 206-6067 UCLA Mathematics Dept. 405 Hilgard Ave. Los Angeles, CA 90024-1555 UUCP:.!{rutgers,ucbvax,sdcrdcf,{hao!cepu}}!ucla-cs!math.ucla.edu!edward ARPA: edward@math.ucla.edu BITNET: edward%math.ucla.edu@INTERBIT