Gargoyle Forum

See the last myth at the bottom of http://www.gargoyle-router.com/wiki/doku.php?id=qos for my thoughts.

I think there are other performance issues, especially with DSL connections that you may not be taking into account.

Perhaps read this:
http://www.diku.dk/forskning/Publikatio ... 04-07.pdf/

and this:
http://research.microsoft.com/en-us/um/ ... -final.pdf

or do a google search for DSL TCP Asymmetry. This is a well documented, and avoidable problem with TCP/IP connections over ADSL. I don't think its a myth considering all the research thats gone into workable resolutions. Without special interventions, highly asymmetric DSL connections lose downlink performance quickly when the uplink is being actively utilized for more then just ACK replies.

Don't get me wrong I love Gargoyle and recently purchased a router off the website to support the project, but it seems there may be ways to get even better performance out of our connections. What are your thoughts about the papers linked above?

The work of Jesper Brouer I studied during the design of Gargoyle QoS. Especially his masters thesis which was published after the article you linked and is a more important work. Search for "Jesper Brouer Thesis" and you will find it. Jesper's main contribution was proper accounting of PPPoE overhead in QoS calculations. Gargoyle uses this work in the form of the "linklayer atm" attribute it applies when you use PPPoE.

The other work you site is from 2001. I have not seen it before but did read it. The methods it suggests (compressing & filtering of ACK packets) are not practical in my view. A lot of water has passed under the bridge since 2001 and if these were good ideas others would have implemented them by now.

Properly accounting for ACK packets in the QoS upstream is important if you want to limit the affect of saturation there on your downlink. You also must consider the link asymmetry when setting QoS classes based on percentages. I gave a correct example of how to do it in the Wiki I pointed you to. If you will follow my advice your uplink will not affect your downlink.

There is nothing inherent about ACK packets that require special prioritization. They should be considered part of the HTTP traffic and prioritized accordingly. They should not be ignored, just considered properly when you are setting up your QoS classes.

I realize I'm reviving an old thread here, so I apologize for that.

I've been using Gargoyle already on a TP-Link router I bought a couple of weeks ago, and it's been working great.

I'm setting up QoS this evening to solve basically the EXACT same problem as the poster. Using comcast with their BS speedboost and backing up basically every evening to Backblaze. I had noticed a while ago that while backing up my internet was totally choked and simply pausing the upload would bring everything back to normal.

I had originally set my Total Upload to 4200 after speed testing and then multiplying by 0.95.

I've since dropped the total upload to 2100, and will see in the coming days if that seems to have solved the issue.

Is there a way to get a better test than the one at SpeedTest.net for upload speed? I assume that one just isn't long enough to slow down after Comcast's initial burst. I'm guessing it's somewhere around the 2.5Mbps mark since that seems to be the speed at which Backblaze normally backs up files when not QoS'ed.

Thanks for a great product!

I use this for my upload testing in QoS development.

http://www.toledorocket.com/perftest/up ... select.asp

You can upload a very large file to this site and get another data point.

Can I revive this thread again?

Can gargoyle stop the internet slowing down to dial up when there is upstream traffic that is only 0.6Mbps speed? Even if I upload at half the speed, the downstream slows down and pings go nuts.

pkm wrote:Can I revive this thread again?

Can gargoyle stop the internet slowing down to dial up when there is upstream traffic that is only 0.6Mbps speed? Even if I upload at half the speed, the downstream slows down and pings go nuts.

Downstream should only slow down (and pings will spike) when upstream is completely saturated. If that's the case, your upload bandwidth limit is set too high... or there's some other abnormality with your router/ISP/QoS Rules, etc. Try reducing your upload bandwidth until uploads no longer affect your download speeds and pings.