В Thu, 10 Jul 2014 19:26:09 +0200 Per Jessen <per@computer.org> пишет:
auxsvr@gmail.com wrote:
There was a script some years ago that configured the IP stack for traffic shaping, named wondershaper or something like that, that would reduce the throughput when sending and set traffic priority accordingly, so that the router does not choke and delay low-latency traffic, such as the DNS requests.
wondershaper works quite well, but it's a big/difficult gun and I don't think bandwidth for DNS requests is really the issue.
The problem is not bandwidth, but queue size and associated latency. PC on LAN sends data with 100Mb/s which results in relatively huge amount of data buffered in router which can only send with 1Mb/s. The solution is indeed to use traffic shaping to restrict bandwidth on a system to 1Mb/s. This won't affect throughput (you cannot transfer more than that anyway) but will minimize latency. I have started with 128Kb/s ADSL so I went through it ...
There's also shorewall, which allows you to configure QoS in many aspects, but I don't know how much effect this may have if the router does not support QoS.
More importantly, if it is indeed a bandwidth issue, the rest of the uplink would have to adhere to QoS too.
Of course, you could also configure the programs that upload data not to saturate the bandwidth, if possible at all.
I do that frequently when I transfer recorded video between my two mythtv backends - if I leave rsync to go at full speed, it impacts watching TV at the same time, so I usually use the --bwlimit option, it works really well in that situation.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org