Gargoyle Forum

I've noticed ACC throttles my speed so is there a way to have it only operate when a QOS classification is 'active'.

I.E
You have three QOS classes for three games
when those classes are active then ACC kicks in and stays active until the QOS classes are inactive

In other words can I use QOS/ACC only when playing games and have it dynamically shut off when no game activity is detected (to fully utilise my bandwidth)

You've just exactly described how ACC operates. Are you experiencing any different?

Can you please show your settings with screenshots?

Lantis wrote:You've just exactly described how ACC operates. Are you experiencing any different?

Yes with ACC disabled I get full download speed with ACC enabled it shaves off roughly 100 KB/s

EDIT: I should add that I'm using 1.6.2 with a DIR-615 rvC1

QOS upload - https://i.imgur.com/hcrPyvU.png
QOS - download https://i.imgur.com/PalD15E.png

Ahh, yep. It takes a little bit of bandwidth to operate. It's a pay to play kind of system I guess.
I now understand your question.

It's not designed to work in the way you describe. It's either always enabled or always disabled.
My experience is that when it is not "active" i.e. Not actively managing ping, my connection will slowly saturate the connection (full speed). I suppose with a slightly smaller pipe (4.8mbits) you're noticing this speed loss a bit more than I do.

I think you just need to decide whether you want it enabled or disabled and what your compromises are. Perhaps PBix will chime in with some other wisdom I have missed.

Oh ok, thanks for the info.
Is there any other method to keep latency low while gaming but utilise full bandwidth when not gaming.

Is there any other method to keep latency low while gaming but utilise full bandwidth when not gaming.

ACC is expressly designed to do exactly this so no there is no other method. In the screen shot you posted the ACC link limit is 4870kbps out of a maximum 4872kbps so ACC is not limiting your speed.

You need to post a screen shot showing the problem you asking about if you want further help with it.

pbix wrote:

Is there any other method to keep latency low while gaming but utilise full bandwidth when not gaming.

In the screen shot you posted the ACC link limit is 4870Mbps out of a maximum 4872Mbps so ACC is not limiting your speed.

You need to post a screen shot showing the problem you asking about if you want further help with it.

I was testing my bandwidth usage when I set up ACC, with ACC on I get roughly 500-510 Kilobytes/second when I disable ACC I get 609 Kilobytes/second
So it appears to someone without advanced knowledge of the system that it limits bandwidth.

Entering incorrect data into your QoS screens can seriously limit your performance. For example, since you have the download limit set at 4870 kbps you can never get more than this amount. If your link will support 610KB/sec you should have this set to around 6200 kbps. That would be one big problem.

Also you manually entered 60ms as your ping time control. What was the automatic value computed by ACC that you overrode with this value and why?

It takes some bandwidth sacrifice to get QoS. This is discussed in the QoS Wiki on this site. Most people want QoS to work at all times and pay the price. If you put a large value here (500ms) than ACC will do nothing unless an RTT class is active. So you will get no QoS and no reduction in download speed which might be what you want.

pbix wrote:Entering incorrect data into your QoS screens can seriously limit your performance. For example, since you have the download limit set at 4870 kbps you can never get more than this amount. If your link will support 610KB/sec you should have this set to around 6200 kbps. That would be one big problem.

6200 Kilobits/s is 775 Kilobytes/s
4,872 kbps = 609 KB/s

pbix wrote: Also you manually entered 60ms as your ping time control. What was the automatic value computed by ACC that you overrode with this value and why?

I'm not sure what the auto value was no Idea where it would have been displayed, I changed it because I was getting spikes to above 1000ms(never happens without QOS)for some reason.