Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!vjs@rhyolite.wpd.sgi.com
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Newsgroups: comp.sys.sgi
Subject: Re: high collisions rates REVISITED
Summary: fixed in 4.0
Message-ID: <99687@sgi.sgi.com>
Date: 25 Apr 91 20:30:29 GMT
References: <9104250127.AA28210@nazgul.physics.mcgill.ca>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 25

In article <9104250127.AA28210@nazgul.physics.mcgill.ca>, loki@NAZGUL.PHYSICS.MCGILL.CA (Loki Jorgenson Rm421) writes:
> 
> 	OK... no one gave me any particularly useful info about what to
> look for insofar as our net problem goes (recap: high collision rates
> on 4D IRIS servers (2-10%) compared to SUNS (0.1% on servers and clients)
> according to "netstat -i").


3.3 and all previous versions of IRIX count both "deferals" and
"collisions" in the Coll column in `netstat -i`.  A deferal happens when a
machine decides to transmit and discovers that the media is already busy.
A collsion happens when a transmitter notices that some other station is
transmitting while it is also transmitting.  Only collisions are counted in
the Coll column in 4.0.

This ancient characteristic (I'm reluctant to call it a "bug" not just
because I did it but because the deferal rate seems useful) was noticed
during testing of new models that can transmit arbitrarily long strings
of packets with 9.6 usec gaps.  They drove the "Coll" rate up to 90% on
other machines.

10% is not a high collision rate, even if you don't count deferals.


Vernon Schryver,  vjs@sgi.com