dtaht
Joined 12 years ago
Karma
555
Submissions
273
Member since
Jun 1
Recent submissions
Comment · 1 year ago
Comment · 1 year ago
Too bitter. I referenced a little of that "adventure" here, in 2021... gfiber was attempting to restart with refreshing their now obsolete hardware... https://blog.cerowrt.org/post/trouble_in_paradise/
Comment · 1 year ago
They laid us all off. They had huge plans - millions of users! Then they intersected reality in KC where all people wanted was 5Mbit service and free TV... There were many, many people working to perfect the settop box for example. We got fq_codel running on the wifi, we never got anywhere on the shaper, the plan was to move 1+m units of that (horrible integrated chip the comcerto C2000 - it didn´t have coherent cache in some cases), I think they barely cracked 100k before pulling the plug on it all....
and still that box was better than what most fiber folk have delivered to date.
At least some good science was done about how ISPs really work... and published.
https://netdevconf.org/1.1/talk-measuring-wifi-performance-a...
Comment · 1 year ago
I´m pretty fond of ¨Ending the anomaly¨: https://www.usenix.org/system/files/conference/atc17/atc17-h...
Comment · 2 years ago
The users that call less post-libreqos are the gamers & zoomers.
I am sorry you are are so down on the lack of motivations care for customer service that many ISPs have. I am thrilled by how much libreqos's customer base cares.
Comment · 2 years ago
I agree that the phrasing in the article is a bit confusing there!
Pie had a severe problem in the rate estimator which was fixed in 2018, in Linux, at least:
https://www.sciencedirect.com/science/article/abs/pii/S13891...
Pie's principal advantage is that it is slightly easier to implement in hardware, it's disadvantages are that it does tail drop, rather than head drop, and struggles to be stable at a target of 16ms, where codel can go down to us and targets 5ms by default. I haven't really revisited pie since the above paper was published.
COBALT in cake is a codel derivative. It is slightly tighter in some respects (hitting slow start sooner), and looser in others (it never drops the last packet in a queue, which fq_codel does.fq_codel scales to hundreds of instances and 10s of thousands of queues, still aiming for 5ms across that target, where it would be easier to essentially DOS that many instances of cake with tons of flows.
Comment · 2 years ago
In a lot of cases older is better.
See also https://github.com/lynxthecat/cake-autorate for an active measurement tool...
Comment · 2 years ago
I would replace the home router with an OpenWrt router.
Comment · 2 years ago
I share your pain. I really really really share your pain.
Comment · 2 years ago
BITAG published this a while back.
https://www.bitag.org/latency-explained.php
It's worth a read.
Comment · 2 years ago
big fan of flent.org and this tool, written in rust - is coming along smartly.
Comment · 2 years ago
Being one of the authors of fq_codel, cake and to a small extent, LibreQos, I remain boggled after 15 years of trying, to get these simple points across..
Have some laughs: https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-...
Comment · 2 years ago
OpenWrt depreciated pfifo_fast in favor of fq_codel in 2012, and have not looked back. It (and BQL) is ever present on all their Ethernet hardware and most of their wifi, no configuration required. It's just there.
That said many OpenWrt chips have offloads that bypass that, and while speedier and low power, tend to be over buffered.
That said, I loved the zero page on the 6502...