tc -s qdisc
qdisc noqueue 0: dev lo root refcnt 2
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc mq 0: dev eth0 root
Sent 1915870461 bytes 1792035 pkt (dropped 0, overlimits 0 requeues 9)
backlog 0b 0p requeues 9
qdisc fq_codel 0: dev eth0 parent :5 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
Sent 126352939 bytes 178972 pkt (dropped 0, overlimits 0 requeues 3)
backlog 0b 0p requeues 3
maxpacket 1506 drop_overlimit 0 new_flow_count 4 ecn_mark 0
new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :4 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
Sent 174596135 bytes 236592 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
maxpacket 83 drop_overlimit 0 new_flow_count 41 ecn_mark 0
new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :3 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
Sent 1166446605 bytes 886189 pkt (dropped 0, overlimits 0 requeues 3)
backlog 0b 0p requeues 3
maxpacket 131 drop_overlimit 0 new_flow_count 5 ecn_mark 0
new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :2 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
Sent 144938955 bytes 188712 pkt (dropped 0, overlimits 0 requeues 1)
backlog 0b 0p requeues 1
maxpacket 322 drop_overlimit 0 new_flow_count 1 ecn_mark 0
new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
Sent 303535827 bytes 301570 pkt (dropped 0, overlimits 0 requeues 2)
backlog 0b 0p requeues 2
maxpacket 0 drop_overlimit 0 new_flow_count 0 ecn_mark 0
new_flows_len 0 old_flows_len 0
qdisc fq_codel 0: dev eth1 root refcnt 2 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 4Mb ecn drop_batch 64
Sent 338513331 bytes 1885759 pkt (dropped 0, overlimits 0 requeues 3)
backlog 0b 0p requeues 3
maxpacket 66 drop_overlimit 0 new_flow_count 1 ecn_mark 0
new_flows_len 0 old_flows_len 0
qdisc noqueue 0: dev br-lan root refcnt 2
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc cake 8005: dev pppoe-wan root refcnt 2 bandwidth 10050Kbit besteffort dual-srchost nat nowash ack-filter split-gso rtt 100ms noatm overhead 34 mpu 64
Sent 296768778 bytes 1881114 pkt (dropped 71489, overlimits 1210302 requeues 0)
backlog 0b 0p requeues 0
memory used: 2773870b of 4Mb
capacity estimate: 10050Kbit
min/max network layer size: 24 / 1492
min/max overhead-adjusted size: 64 / 1526
average network hdr offset: 0
Tin 0
thresh 10050Kbit
target 5ms
interval 100ms
pk_delay 20.3ms
av_delay 1.66ms
sp_delay 3us
backlog 0b
pkts 1952603
bytes 301407281
way_inds 156501
way_miss 200344
way_cols 1186
drops 1269
marks 0
ack_drop 70220
sp_flows 15
bk_flows 1
un_flows 0
max_len 13428
quantum 306
qdisc ingress ffff: dev pppoe-wan parent ffff:fff1 ----------------
Sent 1911135921 bytes 1957135 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc cake 8006: dev ifb4pppoe-wan root refcnt 2 bandwidth 20100Kbit besteffort dual-dsthost nat wash ingress no-ack-filter split-gso rtt 100ms noatm overhead 34 mpu 64
Sent 1896371551 bytes 1946864 pkt (dropped 10271, overlimits 2467180 requeues 0)
backlog 0b 0p requeues 0
memory used: 790144b of 4Mb
capacity estimate: 20100Kbit
min/max network layer size: 22 / 1492
min/max overhead-adjusted size: 64 / 1526
average network hdr offset: 0
Tin 0
thresh 20100Kbit
target 5ms
interval 100ms
pk_delay 960us
av_delay 474us
sp_delay 52us
backlog 0b
pkts 1957135
bytes 1911135921
way_inds 416264
way_miss 158270
way_cols 0
drops 10271
marks 0
ack_drop 0
sp_flows 12
bk_flows 1
un_flows 0
max_len 1492
quantum 613
1 Like
So, as I said earlier, you'll experience jitter up to 20-40ms just due to your low upload speed. So that seems to be the case.
But the jitter in that mid-hop link was hundreds of milliseconds and that's what's really causing your problem. You should try to play closer to you, somewhere that there isn't a link with 100 - 200 ms of variable delay.
i email them and asked to transfer my account to Europe region but they said it is not possible 
but ping plotter is fine before i used to get the same issue with ping hitting 350-450 range and packet loss on ping plotter but now ping plot is fine. and issue was solved by complaints to ISP.
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
At 10Mbps, I expect a single full size packet to last around:
1000 * ((1500 + 34) * 8) / (10 * 1000 * 1000) = 1.2272 ms
So I am not sure whether we are discussing the same data set here. When I run a fast.com speed test on my 95/31 shaped link, I also see upload pk_delay as high as 35ms, so that is not necessarily an issue, especially since for the OP the average delay stays reasonable (av_delay: 1.66ms).
Also I doubt that on a 250ms path a delay variance of 20ms is going to make a difference (well, could be this is pushing things close to breaking already and there might simply be no buffers left for additional delays, this is especially relevant since most/many TCPs seem to start to get somewhat unreliable with path RTTs >= 200ms)
Try to figure out why, plying in europe would easily half your RTT and give you more reserves for unexpected delays.
it is most probably an ISP issue getting packet loss in fornite too with 60ms ping only, upto 10-20% packet loss. But i don't know why no packet loss is showing in ping plotter? 
ping plot is straight line
Well, pingplotter ist just showing an approximation of the path towards the servers, which is nit guaranteed to be identical to the reverse path from the game servers to your home router. If packet loss happens on the reverse leg of the path you will not see it in your pibgplotter traces. There is a great talk by richard steenbergen about traceroute as part of a nanog conference (Nanog 47 IIRC) about the challenges in figuring out network issues with traceroyte/mtr/pingplotter like applications, just google it.
it looks like a issue from ISP side. With VPN game is working fine no stutter or packet loss
Haha, yes I wasn't keeping track of the conversation properly, I thought we were talking about that other thread!
1 Like
+1; good work figurimg this out. This also demonstrates the limits of what SQM can do for you, it can not clean up an ISP's mess... Or put differently, the further away from the true trouble spot the less effective it is going to be. And VPN as work around seems to implicate your ISP's routing, so far away fro your access link.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.