it's not the ping it's interleaving the problem.
Interleaving only has two effects:
a) To alter the bit error distribution, to allow FEC to correct more errors
b) To alter the ping time, aka latency.
If it isn't the ping time, the latency, then the only other part that interleaving can affect is the error rate. But your line doesn't look to suffer many errors.
BUT...
G.INP has an extra impact on latency, that isn't caused by interleacing. If the retransmission mechanism is used after some packets are corrupted (and cannot be fixed by FEC), then there will be some extra latency for those packets only. That appears as
jitter, where the latency varies a lot.
Again, your line doesn't seem to suffer from errors (FECs aren't important here), so I doubt this is the problem.
If you want me to confirm this, you'll need to provide two sets of statistics like last time, but separated over 24 hours.
things get a bit better when i change these things:
What I really meant was: How do you know that your problem is with G.INP if the only change you can make to get rid of G.INP makes things worse? How can you tell that fastpath is certain to be an improvement?
if performs worse than adsl in terms of latency and makes online gameplay like adsl with 7 mb down and 0.256 up 2006 times
When you moved to a "fiber" service, your backhaul probably changed too ... your gaming problems might be being caused there (for example, by sharing a congested link), and the latency of your G.INP access connection plays only a small part.
Did you move ISP when changing to fibre? Do you have any measured "ping" times from the command-line, rather than from within games?
For example, my round-trip ping time can be seen in "ping" commands to the BBC:
C:\>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.246.95] with 32 bytes of data:
Reply from 212.58.246.95: bytes=32 time=12ms TTL=55
Reply from 212.58.246.95: bytes=32 time=13ms TTL=55
Reply from 212.58.246.95: bytes=32 time=13ms TTL=55
Reply from 212.58.246.95: bytes=32 time=13ms TTL=55
Ping statistics for 212.58.246.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms
When my line was fastpath, I'd get times of around 12-13ms. When my line was faulty, and I was given interleaving settings (INP=3, delay=8ms on downstream only), those 13ms times increased to 21ms. Now I'm on G.INP, and my ping times stayed the same: 12-13ms.
In fact, I have some good images to show those last numbers. Let me go and get them off a different computer...
