1
General Discussion / Re: fq_codel latency spikes
« on: May 22, 2019, 10:31:34 pm »
The ethernet link to my Metro-E switch port was set to auto-negotiate on both sides and had negotiated half-duplex 100 Mbps. Switched to 100 Mbps full-duplex. Frontier engineer also removed shaping on my link. Problems seem to have gone away. Wish I knew which change made the difference, but I am extremely happy to have a resolution. I now get the best results with the recommended settings for a 10 megabit link, and an 8.5 megabit pipe limit:
Additional practical testing will be required to verify that it is indeed fixed, but I am optimistic!
muchacha_grande, thank you so much for taking the time to help me. Having a second set of eyes look my rules over made me a lot more confident about calling Frontier for help.
Code: [Select]
10000: 8.500 Mbit/s 0 ms burst 0
q75536 50 sl. 0 flows (1 buckets) sched 10000 weight 0 lmax 0 pri 0 droptail
sched 10000 type FQ_CODEL flags 0x0 0 buckets 1 active
FQ_CODEL target 1ms interval 3ms quantum 1514 limit 10240 flows 1024 ECN
Children flowsets: 10002 10000
BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp
0 ip 0.0.0.0/0 0.0.0.0/0 1 1500 0 0 0
10001: 8.500 Mbit/s 0 ms burst 0
q75537 50 sl. 0 flows (1 buckets) sched 10001 weight 0 lmax 0 pri 0 droptail
sched 10001 type FQ_CODEL flags 0x0 0 buckets 0 active
FQ_CODEL target 100ms interval 5ms quantum 300 limit 600 flows 1024 NoECN
Children flowsets: 10001 10003
Additional practical testing will be required to verify that it is indeed fixed, but I am optimistic!
muchacha_grande, thank you so much for taking the time to help me. Having a second set of eyes look my rules over made me a lot more confident about calling Frontier for help.