Bug 7551
| Summary: | Fluctuating and slow network perfomance | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Charlie G Mentorez (c.gm) |
| Component: | IPV4 | Assignee: | Stephen Hemminger (stephen) |
| Status: | REJECTED INSUFFICIENT_DATA | ||
| Severity: | high | CC: | bunk |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.18.x | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
|
Description
Charlie G Mentorez
2006-11-19 07:12:31 UTC
NEW TEST I found this out: If I run test from a machine with 2.8.18.2 kernel to a machin with older kernel in this test 2.6.16.20 It seem to be ok. 64 octets from 192.168.39.1: icmp_seq=10 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=11 ttl=64 time=0.3 ms 64 octets from 192.168.39.1: icmp_seq=12 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=13 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=14 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=15 ttl=64 time=0.3 ms 64 octets from 192.168.39.1: icmp_seq=16 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=17 ttl=64 time=0.5 ms 64 octets from 192.168.39.1: icmp_seq=18 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=19 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=20 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=21 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=22 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=23 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=24 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=25 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=26 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=27 ttl=64 time=0.3 ms 64 octets from 192.168.39.1: icmp_seq=28 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=29 ttl=64 time=0.3 ms 64 octets from 192.168.39.1: icmp_seq=30 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=31 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=32 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=33 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=34 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=35 ttl=64 time=0.3 ms 64 octets from 192.168.39.1: icmp_seq=36 ttl=64 time=0.3 ms 64 octets from 192.168.39.1: icmp_seq=37 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=38 ttl=64 time=0.2 ms 64 octets from 192.168.39.1: icmp_seq=39 ttl=64 time=0.2 ms But if i make it vice versa then there is a problem. 64 octets from 192.168.117.5: icmp_seq=0 ttl=63 time=0.5 ms 64 octets from 192.168.117.5: icmp_seq=1 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=2 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=3 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=4 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=5 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=6 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=7 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=8 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=9 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=10 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=11 ttl=63 time=0.5 ms 64 octets from 192.168.117.5: icmp_seq=12 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=13 ttl=63 time=0.7 ms 64 octets from 192.168.117.5: icmp_seq=14 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=15 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=16 ttl=63 time=1.4 ms 64 octets from 192.168.117.5: icmp_seq=17 ttl=63 time=0.7 ms 64 octets from 192.168.117.5: icmp_seq=18 ttl=63 time=1.4 ms 64 octets from 192.168.117.5: icmp_seq=19 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=20 ttl=63 time=0.8 ms 64 octets from 192.168.117.5: icmp_seq=21 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=22 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=23 ttl=63 time=0.4 ms 64 octets from 192.168.117.5: icmp_seq=24 ttl=63 time=1.5 ms 64 octets from 192.168.117.5: icmp_seq=25 ttl=63 time=0.9 ms The problem seem to be more obvius when a route are involved. But that could be part of the fact there is some genereal problem and each route then will case more latency. Through our outgoing main internet connection, it was an increas from 0.6 up to 1.9 ms. Checked our contiued log and that shows we have an average on 0.6 to our external routing point. And now we have average 1,9 ms. I will downgrade to 2.6.17.13 and see if the problem then disappear. Could you try and narrow down the kernel change that cause this? with git bisect I know it will be a nuisance, to build all those kernels, but if it is a simple regression, it is much easier to know which change cause it than playing "guess the needle in the haystack" |