Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dtaht99
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
dtaht99
6y ago
I would hope you'd be amused by: https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-... and I am curious if you have considered a fq_codel-like approach to message queuing? Sending a whole socke
2.
▲
by
dtaht99
7y ago
Nice to see you keith. I agree that the network latency part of the equation tends to get too much play, where glass to glass is the better metric. On the other hand the bufferbloat effort started where network latencies were often the domi
3.
▲
A song about the GNU public license
2 points
by
dtaht99
7y ago
|
1 comments
4.
▲
by
dtaht99
7y ago
I keep hoping intel will fix bufferbloat across all their lte/cablemodem/dsl/etc gear. It would improve their end user experience enormously. I even know a few folks that would help....
5.
▲
by
dtaht99
7y ago
The bufferbloat project introduced a great (IMHO) fq + AQM scheme called "cake", which smokes the DOCSIS 3.1 pie in every way, especially with it's new DOCSIS shaper mode in place. It's readily available in a ton of home
6.
▲
by
dtaht99
7y ago
Well, bufferbloat is at it's worst on slow connections (<100Mbit) and 50 dollars worth of router can fix it there in software.
7.
▲
by
dtaht99
7y ago
Yes, that sort of jerky behavior is symptomatic of bufferbloat. Multiple 4G and 5G devices have now been measured as having up 1.6 seconds of buffering in them. They are terribly bloated. It was my hope that the algorithms we used to fix wi
8.
▲
by
dtaht99
7y ago
Your analysis is correct. Smaller buffers are in general better. However advanced AQM algorithms and fair queueing make for an even better network experience. Being one of the authors of fq_codel (RFC8290), it has generally been my hope to
9.
▲
by
dtaht99
8y ago
Well, cerowrt was the big "what can we do to fix ipv6, routing, wifi AND bufferbloat?" project, to produce an existence proof that typical home cpe could be made into something that did all these things. We made sure that everythi
10.
▲
by
dtaht99
8y ago
The code shipped in lede 17.01 that january(2017) and also went Linux mainline at the same time. Everybody on linux using an ath9k and ath10 chip is benefiting today, and it (or a variant) is in multiple commercial products now. I kind of e
11.
▲
by
dtaht99
8y ago
we also added ack filtering to "sch_cake" recently. do hope someone ports it to bsd.
12.
▲
by
dtaht99
8y ago
we designed flent and the rrul series of tests to be able to look at these issues hard and scientifically. See flent.org for the tool.
13.
▲
by
dtaht99
8y ago
Always nice to see you, john. 1) If we had sufficient backpressure in the ISPs provided router network driver, with "BQL" to manage the ringbuffers and fq_codel to do fq + aqm, we're mostly done, at least on the uplink. The h
14.
▲
by
dtaht99
8y ago
That's good basics, but it's all fixed now. Jim's latest blog post goes into exausting detail. https://gettys.wordpress.com/category/bufferbloat/
15.
▲
by
dtaht99
8y ago
if the vpn terminates on the routers... fq_codel now (I cannot remember the kernel version, sorry) can preserve the inner hash of the vpn traffic and manage the flows before they hit the tunnel. This is mostly an ipsec, not openvpn, sort of
16.
▲
by
dtaht99
8y ago
I was essentially in a overwork-induced coma for the last 18 months. The work was carried forward by (many, many) others. I was happy to wake up a few weeks back, and find RFC8290 published, and sch_cake being readied for mainline, and mult
17.
▲
by
dtaht99
8y ago
What router? what ISP? What link technology? What bandwidth? A pointer to your dslreports result? There are plenty of small ISPs that have adopted this stuff... and a few router makers. I am always happy to hear of a bloat free connection.
18.
▲
by
dtaht99
8y ago
Let's see. The turris omnia is a very good router (but only available in europe). For oomph (gbit shaping) people often leverage lede on a pcengines apu2 or run a full distro of pfsense or linux on it.
19.
▲
by
dtaht99
8y ago
It's been happening to everyone. Spread the word.
20.
▲
by
dtaht99
8y ago
I am immensely cheered up by the progress reports contributed by so many on this thread. But, can I ask that if you grok it, go fix it for two friends? Go fix it for a local small business, a coffee shop, or a hotel. And ask your ISP to fix
21.
▲
by
dtaht99
8y ago
DOCSIS 3.1 devices mandate pie, which helps a lot, but it's not as good as fq_codel, nor do they do shaping from the isp, which is kind of needed for all the cable links in the USA I've tried. Get one if you can, though, they are
22.
▲
by
dtaht99
8y ago
85-90% is a better starting point.
23.
▲
by
dtaht99
8y ago
yep. solved - for 6 years in the sqm-scripts and now in cake. (not solved, in docsis-pie) We use diffserv for this, for apps willing to use it. Example: ssh sets the imm diffserv bit for interactive use. cake respects that (I've cited
24.
▲
by
dtaht99
8y ago
totally untrue. fq_codel manages normal torrents just fine in the presence of gamer-style traffic. We tested against torrents in fixing bufferbloat a lot! Pure aqm systems like pie (in docsis 3.1) do pretty well also. cake (per host fq) can
25.
▲
by
dtaht99
8y ago
some comments: 1) BBR is currently not something I'd recommend at home. 2) The hope has always been that the core two bufferbloat-fighting algorithms (BQL, and fq_codel) would end up in the cable, fiber or dsl modem hardware, so that n
26.
▲
by
dtaht99
8y ago
Priority is the wrong way to think about it. Given all the sources of bursts on the internet today, fair queuing (or "flow queuing") has become the way to turn flows back into packets. there's an awful lot of lit on FQ, what
27.
▲
by
dtaht99
8y ago
Bufferbloat happens on high speed links like those but amount of bloat you see is in the 30ms - 60ms range (vs seconds(!!) on home links). Bloat happens mostly (aside from microbursts) on overloaded links - and high speed backbones are typi
28.
▲
by
dtaht99
8y ago
Well, many isp-born devices are provided with that info by the ISP at connect time, so the hope has always been that during configuration they'd just pass (for example) "bandwidth 10mbit docsis" to the network setup routine.
29.
▲
by
dtaht99
8y ago
I wish! QoS could have been a good term to keep using if the existing deployments of it on the Internet it wasn't hopelessly mapped generally to mere packet prioritization (diffserv) which doesn't actually work on today's int
30.
▲
by
dtaht99
8y ago
There were long debates about continuing to use the term QOS for what we did with htb + fq_codel. From: https://www.bufferbloat.net/projects/cerowrt/wiki/Smart_Queu... “SQM” is shorthand for an integrated ne
More ›