NETKEEPER
nklin1.gif (3727 bytes)
|Home|Products|Demos|Tech Support|Top FAQ list| Help Desk Software| CRM Software|


PC too fast for 10Mbit network
Document ID : 000-000454 Created: 2/16/2000 Last changed on: 2/16/2000


For example, a recent problem we had. We were able to prove that some fast
(450MHz +) machines we had on a shared 10Mbit hub actually contributed to
their own downfall - they were so fast at reacting to collisions on the
ethernet and getting the broadcast back on the line that they caused
"artificial" collisions. The effect was that one machine would work fine -
let's say 50 transactions per second (tps). Add another one, and the
performance of both dropped a little - let's say around 45tps each, 90tps
total. Not bad. However, with 5 together, they achieved only about 5tps
each for a total of 25tps - very bad. We threw in a 10Mbit switch and all
achieved 50tps - a tenfold improvement.

This area had operated fine over a long period of time but the machines
had gradually been upgraded so the problem sort-of crept up on us -
particularly as server performance had been enhanced. It was also hard to
pick in a room of around 90 PCs.

How do you elude to issues like that in a document? Equally it could've
been flaky cable, the hub, the server NIC, the configuration of the
server, a faulty NIC or other component in one of the workstations, or
flaky requester software in a workstation (or all), or, or, or......


This solution text WEB page is automatically generated from your knowledge base and service data by NetKeeper Help Desk Software or NetKeeper CRM software. You can customize the pages to your site's look and feel or even include advertisements.

Powered by NetKeeper Help Desk Software
Copyright 1991-2026 Multima Corporation - Conditions of use
Contact us