[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

332.0. "FDDI performance/TCP vs. Sun" by BREAKR::HA () Mon Aug 26 1991 19:53

    My customer is doing an evaluation between our FDDI and Sun's FDDI.
    They have two DECstation 5000/200's, running UWS 4.2, 32 Mb of memory,
    and 40 Mb of memory, respectively.  He's using socket sizes of 48k
    and doing a write() with between 2,000 bytes and 1 MB of data - all
    in memory - no disk activity.  The numbers he's getting are between
    14 and 15 Mb/sec over TCP.  The same program on the Sun is giving him
    18 Mb/sec.  He said he expected to see about 20 Mb/sec. out of our
    stuff.  Can anyone suggest something?  
    
    							Michael
T.RTitleUserPersonal
Name
DateLines
332.1Checksum?STKHLM::TORGNYTue Aug 27 1991 13:568
    Hi,

    Check if SUN is using checksum, rumor is that SUN's default is off
    and ours on. On UDP disabling checksum gives a 75% boost. See
    Digital Technical Journal vol 3 num2 spring 1991 for FDDI performance.

    Regards,
    	Torgny...
332.2from another conferenceOZROCK::FARAGOncl-dns-cml-cmip...aargh!!Wed Aug 28 1991 20:1822
From DNU-PHASEV-IFT notesfile

================================================================================
Note 222.6                       What about FDDI                          6 of 7
STKHLM::TORGNY                                       15 lines  12-JUN-1991 12:08
                            -< TP4 faster than NSP >-
--------------------------------------------------------------------------------
	Hi,

For your reference, here is a summary of the transfer rates I've noticed
between two DECstation 5000/200, connected to a DECconcentrator 500. On all
the occasions the sender run out of cpu.


TCP/IP default		      				18 Mbps
UDP/IP default						20 Mbps
UDP/IP without checksum	      				34 Mbps

DECnet default						12 Mbps
DECnet SDU size 4357, segment buffer size 65535		14 Mbps
DECnet changed from NSP to OSI transport		17 Mbps
DECnet without congestion avoidance			19 Mbps
332.3KONING::KONINGBrivu Latviju!Thu Aug 29 1991 11:265
I'm not sure how you run DECnet without congestion avoidance (other than by
patching the code) but in any case, note that doing so will hurt severely
as soon as you have others on the network along with you.

	paul
332.4I used NCL on DECnet/UltrixSTKHLM::TORGNYThu Aug 29 1991 12:4130
	Hi Paul,

as you see from the DECnet/Ultrix's ncl commands below, it's possible to change
the congestion avoidance attribute. Doing that, I noticed the performance
improvement that's listed in .2

Cheers,
	Torgny...



ncl> show osi trans cong avoi

Node 0 OSI Transport
AT 1991-08-29-17:33:44.669+02:00I583.885

Characteristics

    Congestion Avoidance         = True

ncl> set osi tran cong avoi false
ncl> show osi trans cong avoi

Node 0 OSI Transport
AT 1991-08-29-17:33:55.438+02:00I583.886

Characteristics

    Congestion Avoidance         = False

332.5why selfish optimization worksDELNI::GOLDSTEINNetworks designed while-u-waitThu Aug 29 1991 17:1312
    re:.4
    Yes, it may run faster if you turn congestion avoidance off...
    
    YOUR node will run faster!  But that's because it's "hogging" the
    network.  Others will slow down and you won't, so they'll be making way
    for you.  This is called "selfish optimization".  It makes a good demo,
    but a bad network.  Total throughput amongst all nodes declines; the
    amount you gain is less than others lose.
    
    Of course, TCP/IP lacks congestion avoidance while DECnet V has it, so
    I suppose it's fair to turn it off when the network is mostly TCP....
    That's also one reason why IP fans haven't added it.  Who'd go first?
332.6It was for a DEMOSTKHLM::TORGNYFri Aug 30 1991 06:4312
    > YOUR node will run faster!  But that's because it's "hogging" the
    > network.  Others will slow down and you won't, so they'll be making way
    > for you.  This is called "selfish optimization".  It makes a good demo,
    > but a bad network.  Total throughput amongst all nodes declines; the
    > amount you gain is less than others lose.

    Exactly, and I did this at a symposium on high speed communication and
    I didn't want OSI to look bad compared with IP on the private FDDI ring
    we used.

    Torgny...

332.7particularsBREAKR::HAWed Sep 04 1991 18:4713
    Here's what finally worked:
    
    # dbx -k /vmunix
    (dbx) assign tcpcksum=0
    (dbx) assign tcp_sendspace=32768
    (dbx) assign tcp_recvspace=32768
    (dbx) quit
    
    I now get 18-19 Mb/s using TCP.  To boost UDP performance the variables
    are called udpcksum, udp_sendspace, and udp_recvspace, respectively.
    
    								Michael