Re: Ethernet Characteristics re: packet loss
Tony,
What you were testing was obviously a full duplex setup.
In a the older CS/MA-CD half duplex environment the normal effective
transfer bandwidth was about 30% on segments that have a large number of
nodes. On segments that had a low number of nodes, the theoretical
effective utilization was 40%. This limitation was because of collisions
on the segment.
Full duplex setups do not support collisions. With non-blocking Ethernet
switches, it should not be hard to get 100% utilization between any two
nodes. For full duplex segments with large numbers of nodes, close to 100%
effective utilization can be achieved if all of the nodes are sending to
each other equally. When any one node is the destination of an aggregation
of multiple other nodes, such as on a workstation/server LAN the bandwidth
utilization is limited by the bandwidth of the destination node. With
properly implemented flow control, the effective aggregate bandwidth on
source nodes will match the destination node at close to 100%.
Thank you,
Roy Bynum
At 11:50 AM 3/19/01 -0500, Stout, Tony wrote:
>I have a quick question.... someone made a statement that it is a
>characteristic that once you go above 40% LAN capability, the you will begin
>to lose packets. This doesn't seem to hold water with me. I recently
>performed a test whereby we injected packets at 100%, 75%, 50%, 25% 10% & 5%
>network capability. We had 2 laptops, 1 desktop (PIII dual processor), a
>LAN Analyzer, and a SmartBits 200 generator -- at 100% both the laptops 40%
>of the packets we were sending -- the desktop captured 70% --- in both cases
>the application running on the platforms was using 100% of the processing
>time. -- my suspicion is that this is where the packets are being loss -- in
>the processing arena.
>
>Can you shed any light on this?
>
>Thank you,
>
>Tony Stout
>JITC
>Information Systems Test Director
>
>Phone: 301-744-2690
>Mobile: (301) 399-9078
>Fax: 301-744-2688
>
>JITC Webpage: http://misd.ncr.disa.mil/misd
>
>
> <<Tony Stout (E-mail).vcf>>