On Wed, 3 Aug 2016, Loganaden Velvindron wrote:
My conclusion from playing with fq_codel, cake, and txqueuelen 0 hacks
is that as a pre-requisite, we need to have ISPs that are able to give
latency with little variations to various places around the earth.
Proving that any QoS on high
You could also use a custom kernel that would allow you to add
fq_codel/cake then add custom rules to it.
I would advise a setup such as: AFWall to run scripts depending on whether
it's WiFi or Mobile (3G/4G). The script would be a simplified debloat.sh
just adding simple tc fq_codel/cake
I went further, and rooted the android phone.
Then I set the txqueulen to 0 on ccimni0 and wlan0.
Here are the results:
https://www.dslreports.com/speedtest/4569339
https://www.dslreports.com/speedtest/4569379
Despite disabling the txqueuelen, The inbuilt TX/RX buffers are still
pretty high:
Hi Sebastian,
After reading about how much has been done in the latest kernel, I
decided to find a quick and easy way to get 3g mobile internet. I went
to another provider, and just put the SIM in an android one (Karbonn
Sparkle V) smartphone running Android 6.0.1.
Then, I activated the
I think what's happening is that regardless of what I apply on the
OpenWRT router, the modem is queueing & possibly re-ordering packets
its way.
The huawei B6A modem has a linux firmware. If I could access the cli
to reduce the tx length, I think that this may help.
Also, the 3g connection
>>
>> It's interesting to see the saw tooth pattern for the upload. This was
>> not the case when the target was 5ms, which I believe was calculated
>> based on a 100ms worse rtt.
>
>
> I just noticed you use the dslreports pre-canned profiles for measuring. I
> would recommend against doing
Hi Loganaden,
> On Jul 24, 2016, at 19:13 , Loganaden Velvindron wrote:
>
> On Sun, Jul 24, 2016 at 6:40 PM, moeller0 wrote:
>> Hi Jonathan,
>>
>>> On Jul 24, 2016, at 13:28 , Jonathan Morton wrote:
>>>
>>>
On 24 Jul, 2016,
Hi Loganaden,
this is exactly the right idea; interval basically defines the “reaction time”
window, or the time the endpoints of a connection minimally require to actually
react to the drop/mark signal. So on a slow link with RTTs in the order of
300ms set interval to 300ms.
Target should be
I am getting A to A+ for quality when setting the interval to 350ms.
http://www.dslreports.com/speedtest/4520977
I am getting - to C for quality when setting the interval to the
default value of 100ms.
http://www.dslreports.com/speedtest/4520957
___
Hi Sebastian,
Since dslreports disable the ping due to high latency:
I did a ping test during the test:
--- youtube-ui.l.google.com ping statistics ---
61 packets transmitted, 61 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 336.631/369.733/493.473/30.946 ms
It looks to me
I've set the interval to 350ms, by using advanced option:
Result is better:
http://www.dslreports.com/speedtest/4520697
I will submit a patch for sqm-luci so that the interval is
configurable easily via web ui for African countries where the latency
tends to be of the order of 300ms to 600ms,
After going through:
https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-06
I think that I should remove the itarget and etarget, and set the
Interval rather to 500ms.
The _interval_ parameter has the same semantics as CoDel and is used
to ensure that the minimum sojourn time of packets
> It seems the initial burst like behavior from the earlier test was a
> false positive; these test are still not beautiful, but at least they do not
> indicate that HTB+fq_codel as configured on your system do not suffer from
> uncontrolled bursty-ness. Unfortunately, I have no real
13 matches
Mail list logo