Hi roman921 -
When you say "freeze up" do you mean the whole computer (i.e., mouse does not move, etc) or do you mean that the network activity drops to 0% and then jumps up to say 10% (just throwing out numbers here) and then will transition back to the normal 1% rate?
Thank you for using Intel Ethernet.
Thank you for attention to my issue. Since the server is in data center and I acces it remotely, I unfortunately cannot clarify other freeze symptomps that may or may not take place there. I can only see the issue retroactively, and from software side it was isolated to TCP socket operation. The application is waiting for data from socket and while normally it receives data in small increments, at the issue time there is a delay and then a large buffers comes in.
For example, time and number of bytes received:
/* Here comes a delay of 0.77 seconds */
This pattern repeats all the time: a delay, then a small "normal" buffer is received and next to it there is a large buffer, which may refer to several seconds of traffic.
Hi roman921 -
That is definitely odd pattern you are seeing there. I would recommend that a network sniff be taken for this connection and see if there is any packet loss or retransmission going on during this pause in the traffic. There are a number possible causes including an intermediate switch dropping frames (this is normal for some switches through an algorithm called RED or other associated algorithms) to an issue with a card.
@ MarkH - would you recommend any additional action for roman921?
Thanks, I will try to use sniffer to get some details. Apart from that, is there any chance that hard drive activity affects in some way networking, such as throttling. It was a pure guessing but I did have a suspicion that there is a correlation between peak disk activity and communication delays. Anyway, I am going to use sniffer to gather more information, thanks for your help.
If the data being transferred is being written to a hard drive then that could be your bottleneck. If you run short on physical RAM and end up with pages being swapped between RAM and the hard driver, the bottleneck could be made worse.
Once you look at the Ethernet trace, you might have a better idea about whether the network connection itself seems to be working properly.