Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Submission + - Starlink cuts P99 latency by 60%, deploys FQ_Codel on WiFi (starlink.com)

mtaht writes: Starlink has set itself a goal of 20ms latency across their entire LEO network, and published an update as to how far they have come, and how far they are going, tackling "Dumb stuff driven by non-physical limitations in our system" – "unneeded processing delays, unoptimized buffers, or unnecessary packet drops that force retries. Buffers across our network have been right sized to reduce bufferbloat, and queueing algorithms have been improved to increase capacity on our gateway links from the ground to satellites. Our WiFi latency has been improved, with the addition of active queue management, fq_codel, to the Starlink WiFi router. With active queue management enabled, when one person on your WiFi is downloading a big file, and another is playing a game, the game latency will not be affected by the download".

Submission + - New FCC Broadband standards should consider working latency (ycombinator.com)

mtaht writes: In the 2024 FCC 706 process report, released a few days ago — Broadband "Working Latency" finally became an issue, in light of the old pathetic FCC 100ms requirement not accounting for bufferbloat & only measuring idle latency. The worst 10 ISPs in the USA had over one second of latency under load at the 99th percentile!.

Comment Re:People are seriously underestimating the AI dat (Score 1) 98

I have long advocated that somehow the companies that have built their businesses on the backs of open source developers find some way to reward them on the backs of the IPO, like redhat did, in 1999. This is not that. For a one time investment in stock, you too, can support development of our new AI overlords.

Submission + - Starlink gen4 teardown and benchmarking in Ukraine (olegkutkov.me)

mtaht writes: Oleg Kutkov, who when not dodging missile strikes in Ukraine, makes his living from repairing bullet torn Starlink terminals, does a teardown and analysis of the network performance of the gen3 vs gen4 terminal.

Comment OpenWrt on X86 for the FW, Ath9k for wifi (Score 1) 150

I still use venerable WNDR3800s (15 years old now) as APs. (I had about 30 left over after the make-wifi-fast project ceased) They do 300Mbit, no binary blobs, have good range, stay up forever (I know of people with 3+years uptime), and are the best known fq_codel implementation across the board.

Elsewhere I kind of gave up on an all-in-one unit for gbit+ networking and went with the evenroute pro (sadly deceased, but the company was VERY good about upgrading their userbase to mainline OpenWrt) - but any x8664 mini-pc with few ethernet ports suffices nowadays.

The mt76 and mt79 wifi chips stablized a lot in the past year (and have way less "blob" to them than the qcomm gear - so they are looking like the successor to the ath9k for me.

Comment OpenWrt has the best wifi (Score 2) 150

fq_codel native on the mt76 and mt79 chips is the bomb. https://blog.cerowrt.org/post/... OpenWrt has CAKE also. I am seeing a lot of *sense fanbois complaining that fq_codel shaping inbound on BSD is seemingly buggy, and those that went from opnsense to OpenWrt, much happier with CAKE on the QoE front. I have been trying to find someone with BSD experience for ages to help figure out what is going wrong on that OS in this department.

Comment Re:I remember still when we were the revolutionari (Score 1) 59

Borland I was working on the interbase database. Zero comms with the compiler team. The gcc patches I attempted to get out were to get our (Unix) code built on some obscure platform (this was 1992). Ixnayed. Any sufficiently big software company will have some potential conflict with open sourcing anything. Most recently, the authors of RFC9406 - an attempt at an open document, prohibited from working directly on a Linux implementation.

Comment Re:I remember still when we were the revolutionari (Score 1) 59

SCO did not want anyone to work on Linux. In fact, got a restraining order against me or 3 years against working on multiprocessor systems dSybase did not want anyone working on postgres Mediaplex did not want anyone contributing to apache. That was my life 1992-2000. I am glad your life was better. Android consciously ripped out all gplv2 code from userspace Google attempted to get dnsmasq relicensed. Google was apache only by default. 2018 apple would not permit gplv3 code Today gplv3 is essentially banned everywhere I have worked. OpenWrt derivatives - Comcast rdk-B, and a zillion corps that use it, rip out all the gpl components and essentially prohibit their devs from contributing back to it.

Slashdot Top Deals

Elegance and truth are inversely related. -- Becker's Razor

Working...