• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10


  • Subject: Re: Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10
  • From: "Peter Sichel" <email@hidden>
  • Date: Thu, 12 Oct 2006 10:36:13 -0400

On 10/12/06, Heiko wrote:

>Short description: The Mac is a OS X.4 client with 100MBit network
>connection (172.27.2.127), and the Sun is Solaris 10 AFP-Server
>(Ethershare) with a 1000MBit network connection (172.27.1.40). The
>problem only occurs while reading data from the Sun.

Solaris uses Mentat/TCP while Mac OS X uses a variation of the BSD
stack.  Both are fairly tunable but may have  different assumptions
about high bandwidth low latency pipes.

>The Mac acknoledges data packets from the Sun very lazily, meaning
>the Sun sends up to 6 packets, the Mac ack's just one. This way the
>retransmission queue of the sun fills up with unacknoledged packets,
>forcing the Sun to throttle down.
>Some packets later, the Sun only sends new packets if prior packets
>are acknoledged.

One obvious suggestion would be to turn off delayed ACK on the Mac OS X box.

sudo sysctl -w net.inet.tcp.delayed_ack=0

You can do this using UNIX sysctl or my own IPNetTunerX
(www.sustworks.com) which will give you better visibility into the
parameters available and the effect of tuning.

I noticed just now on 10.4.8 that the value for delayed Ack is "3" which
surprises me.  Previously I only noticed it could be "on" (1) or
"off" (0).  This may have some bearing on why Mac OS X is ACKing so lazily.


>Now the Mac sends acks for more then one packet at a time (good
>thing), but delays the send about 500microseconds...this gets worse,
>until the delay is about 200ms (milliseconds!). As you can imagine,
>the throughput is near zero.

This certainly looks like a delayed_ack issue.  I've just never seen the
delay become quite so large.  Are your two machines directly attached to
the same LAN, or is there a router between them?  I ask because TCPs
slow start behavior is different for a host on a non-local network.

>Has anyone heard of such a problem before?

There are some known tweaks to speed up Samba file copying speeds.
Hopefully the above pointers will get you started.

Kind Regards,

- Peter


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10
      • From: "Justin C. Walker" <email@hidden>
References: 
 >Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10 (From: Heiko <email@hidden>)

  • Prev by Date: Re: How to find the primary network interface?
  • Next by Date: Re: Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10
  • Previous by thread: Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10
  • Next by thread: Re: Strange TCP-networking problems with Mac OS X 10.4 and Solaris 10
  • Index(es):
    • Date
    • Thread