Community
cancel
Showing results for 
Search instead for 
Did you mean: 
MPati8
Beginner
308 Views

Weird latency issue NUC7i5BNK Running CentOS

I bought the NUC to use as a server, so I installed CentOS on it and noticed some odd issues with it responding to pings within my LAN. It cycles from a low ping time to high latency responses and circles back. When I ping Google DNS or public sites I don't have this issue. has anyone seen anything like this before?

 

I'm running 16GB of RAM and from what I can see the newest BIOS firmware: BIOS Update [BNKBL357.86A]

 

ping 192.168.1.28

PING 192.168.1.28 (192.168.1.28) 56(84) bytes of data.

64 bytes from 192.168.1.28: icmp_seq=1 ttl=64 time=3.73 ms

64 bytes from 192.168.1.28: icmp_seq=2 ttl=64 time=122 ms

64 bytes from 192.168.1.28: icmp_seq=3 ttl=64 time=139 ms

64 bytes from 192.168.1.28: icmp_seq=4 ttl=64 time=162 ms

64 bytes from 192.168.1.28: icmp_seq=5 ttl=64 time=185 ms

64 bytes from 192.168.1.28: icmp_seq=6 ttl=64 time=209 ms

64 bytes from 192.168.1.28: icmp_seq=7 ttl=64 time=26.9 ms

64 bytes from 192.168.1.28: icmp_seq=8 ttl=64 time=50.9 ms

64 bytes from 192.168.1.28: icmp_seq=9 ttl=64 time=71.4 ms

64 bytes from 192.168.1.28: icmp_seq=10 ttl=64 time=97.5 ms

64 bytes from 192.168.1.28: icmp_seq=11 ttl=64 time=117 ms

64 bytes from 192.168.1.28: icmp_seq=12 ttl=64 time=143 ms

64 bytes from 192.168.1.28: icmp_seq=13 ttl=64 time=165 ms

64 bytes from 192.168.1.28: icmp_seq=14 ttl=64 time=189 ms

64 bytes from 192.168.1.28: icmp_seq=15 ttl=64 time=213 ms

64 bytes from 192.168.1.28: icmp_seq=16 ttl=64 time=32.6 ms

64 bytes from 192.168.1.28: icmp_seq=17 ttl=64 time=51.5 ms

^C

--- 192.168.1.28 ping statistics ---

17 packets transmitted, 17 received, 0% packet loss, time 16015ms

rtt min/avg/max/mdev = 3.737/116.708/213.503/65.364 ms

ping yahoo.com

PING yahoo.com (72.30.35.9) 56(84) bytes of data.

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=1 ttl=50 time=65.4 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=2 ttl=50 time=63.1 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=3 ttl=50 time=60.7 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=4 ttl=50 time=68.2 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=5 ttl=50 time=64.9 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=6 ttl=50 time=63.4 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=7 ttl=50 time=67.4 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=8 ttl=50 time=63.2 ms

64 bytes from media-router-fp1.prod1.media.vip.bf1.yahoo.com (72.30.35.9): icmp_seq=9 ttl=50 time=63.4 ms

^C

--- yahoo.com ping statistics ---

9 packets transmitted, 9 received, 0% packet loss, time 8009ms

rtt min/avg/max/mdev = 60.772/64.463/68.202/2.194 ms

 

ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=20.2 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=17.6 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=18.3 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=16.3 ms

64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=15.5 ms

64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=13.7 ms

64 bytes from 8.8.8.8: icmp_seq=7 ttl=54 time=22.8 ms

^C

--- 8.8.8.8 ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 6005ms

rtt min/avg/max/mdev = 13.731/17.816/22.844/2.817 ms

Tags (1)
0 Kudos
6 Replies
AlHill
Super User
97 Views

Only Windows 10 is supported on your NUC:

https://www.intel.com/content/www/us/en/support/articles/000005628/intel-nuc.html

 

Go to linux.org for support with your OS.

 

Doc

 

Konstantin
New Contributor I
97 Views

"Supported" on this page means "tested by Intel", right? It doesn't mean that Linux doesn't work on NUC, or possible hardware issue. For example NUC8i7BEH (like many other models) officially "supports" only Windows, but works well on Linux.

Ronny_G_Intel
Moderator
97 Views

Hi MPati8,

 

I am not an expert on "ping" command, I only know in general how it works and I am having the exact same behavior with 2 different NUCs machines: NUC7i5BNK and NUC6iKYK. I also asked a peer of mine to run the same test on a different local network and he had the same results, all systems are running Windows* 10.

I am guessing this is the expected behavior. See the attached image with my results after running 50 "pings".

 

Regards,

Ronny G

 

MPati8
Beginner
97 Views

That’s interesting that it’s happening on NUCs running windows as well. The NUC is the only thing on my network that has this behavior. Everything else from MBP, Sonos speakers and smart anything have a response time of under 10ms consistently, as with most things in a small home network.

Ronny_G_Intel
Moderator
97 Views

Hi everyone,

 

Apologies, I said that I was posting an image with my results but it was never visible, please see below:

 

PingS.bmp

Regards,

Ronny G

 

Ronny_G_Intel
Moderator
97 Views

I havent done much research on my own network about this issue but if the ping fluctuation is only a problem on LAN, then it could be any number of things and not necessarily the NIC.

 

I would recommend the following:

  • Review CPU Process history: If you have high CPU usage during the ping fluctuations, then there may be a process/service causing this. 
  • Did you run a tracert? This could pinpoint if there is an issue.
  • If you want a good look as to what is going on…there is tool WinMTR: WinMTR download | SourceForge.net this is a Windows* tool as far as I can tell, perhaps you can try it on a different system that is based on Microsoft* or look for an equivalent Linux* version.
  • If no packets loss in your ping, that’s good. Pings are considered low priority traffic.

 

I hope this helps,

Ronny G

  

Reply