On Tuesday 21 July 2009, Trond Myklebust wrote: > This would be where you are losing your performance. 1998.933 ms rtt > means that you are seeing a 2 second delay from the instant the RPC > client pushes the request into the socket to the moment that socket > receives a reply from the server. > > Basically, you have either a _very_ slow server, or (more likely) a The server should be fast enough. > networking problem. A tcpdump ought to be able to show what the problem > is: whether it is the packets getting ACKed very slowly, and/or if you > have dropped packet issues or if it is truly a problem with the server > taking a long time to reply. I did run a traceroute alongside and that did not show packet loss, but I do now see some TCP data loss events and retransmits of segments in 'netstat -s', and "TCP Previous segment lost" with varying time gaps in wireshark. So I guess it is indeed a networking problem. As I see it both with wired and wireless on the client, the problem must be either in the server or the switch near the server (replacing the cable from the server did not help). I suspect the integrated e1000e NIC. Guess I'll add an extra NIC in the server soon to see if that helps. Thanks a lot for your help! P.S. I see one strange thing in wireshark: NFS (or the networking stack) seems to switch between small and large package (?) sizes occasionally in the same stream. Is that normal? Source Destination Protocol Info [...] <server> <client> RPC Continuation <server> <client> RPC Continuation <client> <server> TCP kink > nfs [ACK] ... <server> <client> RPC Continuation <server> <client> RPC Continuation <client> <server> TCP kink > nfs [ACK] ... <server> <client> TCP [TCP segment of reassembled PDU] <server> <client> TCP [TCP segment of reassembled PDU] <client> <server> TCP kink > nfs [ACK] ... <server> <client> TCP [TCP segment of reassembled PDU] <server> <client> TCP [TCP segment of reassembled PDU] <client> <server> TCP kink > nfs [ACK] ... [...] <server> <client> TCP [TCP segment of reassembled PDU] <server> <client> RPC Continuation (total: 65535 bytes) <client> <server> TCP kink > nfs [ACK] ... <server> <client> RPC Continuation <server> <client> RPC Continuation <client> <server> TCP kink > nfs [ACK] ... [...] -- 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
