Hi Thorsten, Thorsten Meinl schrieb: > Ich have to computer connected via Gigabit Ethernet via just one switch. I did > some experiments with dd from one computer to the other and got only rates of > about 10MB/s. Looking further at it, it looks quite strange: for the first > few seconds the transmission rate is at about 100MB/s which one would expect. > Then it drops down to about 20MB/s and then to only a few megabytes. Using > Wireshark I found out the following (this is a dump from the client that > writes the 10GB file): [...] > There is a 0.2s delay between packet 311 and 312 and it is totally uncleat to > me what could be the cause, as the reply for the last write call in 303 > arrived in 311. So what is NFS waiting for (This situation occurs frequently > and I assume this is the cause of the very low throughput). > The server storage system and the network cannot be the problem because using > sshfs I get rates of about 80MB/s and the bottleneck here is the CPU at the > client side. > I also tried TCP and there the rates are slightly better but still do not > exceed ~20MB/s. > Does anyone have an idea or any hints how I can debug this further? And yes, I > already tried the various suggestions in the FAQs like increasing receive > buffer sizes and such. Just a blind guess. sshfs is using TCP while your NFS setup seems to be UDP, so there might be the problem. Maybe your network is temporarily congested and the egress switch is notifying the send to back off? There should be a specific ethernet frame visible on the server side which I guess wireshark should be able to see these pause frames (http://en.wikipedia.org/wiki/Pause_frame) Sorry if that's not helping much, but that's just my very first quarted educated guess. Cheers Carsten -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
