sgf@cfm.brown.edu (05/18/89)
In a previous posting I stated that our 3.5 3/280 server was maxing out its ie during excessive nd paging. After receiving info from an ether-guru at Sun I am inclined to believe that it is possible that the ether was saturating. My bandwidth-use info came from ether(3r) stats on a diskful 160, and I now think that I should get my hands on an etherhound for more accurate monitoring. In either case the best thing to do is to have >= 8MB of memory in the clients and then to slap on local disk for swap. Making the network look like a disk for data private to the client is a waste of server cpu and network bandwidth.