ACC issue
Posted: Sat Nov 03, 2012 2:01 pm
Using 1.5.5 at a bar. 12mbit link.
Today link was limited to ~2 Mbit.
Without router, link returned 11.5 Mbit.
So I checked DL QOS page.
Initially I had been running QOS with ACC on upload and download at the measured rates. Like I do in every other environment; it's the best.
Today, for whatever reason, Gargoyle in this deployment measured pingtime to ISP (stock) gateway at 400+ms, which resulted in ACC throttling back the 12Mbit connection to 2Mbit, trying to fight the latency. I was notified, saw it, and fixed it.
I changed the ping target to a local ISP DNS server, typically 15ms away.
This fixed the problem for a few minutes, but it soon shot up to over the pingtime limit and ACC kicked in again, throttling to "fair limits" of a small percentage of link speed.
So ultimately I shut all QOS off and the line returned to 11.5Mbit speeds. Did I have time (or forethought) to measure actual latency to ISP gateway or alternate target before I shut QOS off? No.
And really, no matter what the latency, if it comes back to 97% of advertised rate (from 16% throttled by ACC seeing 400+ms) within seconds after shutting down all QOS, you'll do that.
Anyway, wherever this artifact came from, it resulted in the linespeed being throttled by 85%.
So I'm reporting my first ever problem with Gargoyle.
I can easily recreate the situation; I just don't have alarms in place to tell me when the connection gets throttled to 2Mbit again. This happened for a few days. How/why could the router observe 400ms pingtimes to the ISP gateway via cable modem not under load?
What kind of ISP gateway is over 400ms away? Cable modem? Get real.
We don't know. The consequent throttling we do know about.
Pbix login details in private message...
Today link was limited to ~2 Mbit.
Without router, link returned 11.5 Mbit.
So I checked DL QOS page.
Initially I had been running QOS with ACC on upload and download at the measured rates. Like I do in every other environment; it's the best.
Today, for whatever reason, Gargoyle in this deployment measured pingtime to ISP (stock) gateway at 400+ms, which resulted in ACC throttling back the 12Mbit connection to 2Mbit, trying to fight the latency. I was notified, saw it, and fixed it.
I changed the ping target to a local ISP DNS server, typically 15ms away.
This fixed the problem for a few minutes, but it soon shot up to over the pingtime limit and ACC kicked in again, throttling to "fair limits" of a small percentage of link speed.
So ultimately I shut all QOS off and the line returned to 11.5Mbit speeds. Did I have time (or forethought) to measure actual latency to ISP gateway or alternate target before I shut QOS off? No.
And really, no matter what the latency, if it comes back to 97% of advertised rate (from 16% throttled by ACC seeing 400+ms) within seconds after shutting down all QOS, you'll do that.
Anyway, wherever this artifact came from, it resulted in the linespeed being throttled by 85%.
So I'm reporting my first ever problem with Gargoyle.
I can easily recreate the situation; I just don't have alarms in place to tell me when the connection gets throttled to 2Mbit again. This happened for a few days. How/why could the router observe 400ms pingtimes to the ISP gateway via cable modem not under load?
What kind of ISP gateway is over 400ms away? Cable modem? Get real.
We don't know. The consequent throttling we do know about.
Pbix login details in private message...