Why We Run FreeBSD current at Netflix – Drew Gallatin on HackerTube: recommended by 1 Hacker News commenter across 1 month, 2024–2026.
talk · advanced · dated
Netflix engineer Drew Gallatin explains why the company runs FreeBSD-current on its CDN. He describes the team, how they track upstream, their contributions and performance milestones, and a bug causing a 20% performance regression.
HN cites it as the Netflix case for staying close to -CURRENT and upstreaming changes.
“they recommended both upstreaming and keeping as close to -CURRENT as possible”
4 Hacker News comments link this video. Each one links back to its thread.
In addition to the vendor summit, Netflix gave a tech talk recently where they recommended both upstreaming and keeping as close to -CURRENT as possible "Why we run FreeBSD CURRENT at Netflix": ▶ this video
in “Why Dell's ThinOS Runs on FreeBSD” · View on HN
> Or just run -current in production, like we do.[0] If you develop, it's probably best to do that against current [1], but if I'm running a web, mail, file, database, etc , server there is IMHO very little advantage to doing so. Most folks aren't trying to push >400Gbps. [0] ▶ this video [1] [link]
in “FreeBSD 14.4-Release Announcement” · View on HN
Your comment suggests that FreeBSD is a thing of a past and no longer capable of "quality networking", due to poor WiFi support. I can only agree with the poor WiFi support part. But WiFi is by no means something you can judge networking stack dedicated for servers. FreeBSD was never designed for consumer hardware networking. There were a few "desktop distros" but all have more or less died, and the few FreeBSD-based "storage distros" moved to Linux after FreeBSD changed its upstream for ZFS. And I'm saying this as someone who made a lot of effort to use FreeBSD on laptop over the years, and a current user of 15.0-CURRENT on ThinkPad. But FreeBSD was and is THE choice for high-bandwidth wired networking. Netflix is both an early adopter and an active contributor to FreeBSD's networking codebase. They hack FreeBSD[0] to achieve cool numbers over and over[1][2]. Intel's device mentioned by you - AX200 - works "fine" on my ThinkPad, for a few months now. The device was on supported hardware list for more than a year prior, but the actual driver wasn't covering all vendor/device id pairs (different flavors of hardware or behavior all known as "the same" chip; this is a major problem with consumer devies since chip outages started). That said, by "fine" I mean that I can use the card and finally can connect to 5GHz networks and avoid disruptions related to 2.4GHz congestion. But FreeBSD is still incapable of utilizing speeds offered by modern WiFi specifications. Even with 5GHz co
in “FreeBSD 13.4-Release” · View on HN
Its here, in this talk in from this year. ▶ this video They did 800gbps in 2022 and now seems to be focusing on low power usage with arm.
in “Serving Netflix Video at 400Gb/S on FreeBSD [pdf]” · View on HN