Linux BPF Superpowers: a talk by Brendan Gregg of Netflix at Facebook's Performance@Scale event about Linux enhanced BPF (aka eBPF) for performance analysis.
12 eBPF-Powered CLI Utilities That Every Modern Linux Sysadmin Should Master
Classic Linux tools are always there, but eBPF is the natural upgrade as it looks directly in the kernel. Once you start using these tools, it’s hard to imagine managing Linux systems without them.
eBPF and Kubernetes: Little Helper Minions for Scaling Microservices - Daniel Borkmann, Cilium
mitchellh/libxev
libxev is a cross-platform, high-performance event loop that provides abstractions for non-blocking IO, timers, events, and more and works on Linux (io_uring or epoll), macOS (kqueue), and Wasm + WASI. Available as both a Zig and C API.
SpeedCurve by Embrace | Website Performance Monitoring
User focused observability for mobile and web. See how people experience the speed of your website, then identify and fix performance issues.
clem 🤗 on Twitter / X
We just released an hf CLI extension to detect the best model/quant for a user's hardware and then spins up a local coding agent. Time to go local/private/free/fast for your agents thanks to open-source! pic.twitter.com/LcVJzGCqWx— clem 🤗 (@ClementDelangue) March 17, 2026
BrowserBench.org — Browser Benchmarks
Speedometer is a browser benchmark that measures the responsiveness of web applications. It's maintained by major browser engine developers under an open governance model.
MySky: Open, Controllable Feed Infrastructure for the Atmosphere - AT Protocol
MySky is an algorithmic feed running on Bluesky, with a settings panel that shows you the whole ranking pipeline exactly as it runs.
Compiling Models to Megakernels
Fine-grained synchronization, deep pipelines, and zero kernel launch overheads, automatically.
Multi-process Firefox brings 400-700% improvement in responsiveness | TechCrunch
Earlier this summer I wrote about Mozilla's efforts to rollout a multi-process architecture, codename Electrolysis, for Firefox. In the months since,
binhnguyennus/awesome-scalability
The Patterns of Scalable, Reliable, and Performant Large-Scale Systems
An inside look at gRPC - performance, testing and load balancing, Mon, Jul 22, 2024, 6:00 PM | Meetup
Agenda: 5:30 Doors open 6:00 - 6:05: Announcements 6:05 - 6:30: The rest of the iceberg: performance and testing of the gRPC libraries - Ashley Zhang and AJ Heller 6:30 - 7
Reading a Performance Profile: Field Guide
An interactive field guide to the Chrome DevTools Performance panel: waterfall, flame chart, LCP, CLS, INP, and the Insights panel.
RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win | TechCrunch
Editor's note: With all of the debate lately between RSSCloud versus PubSubHubbub, we wanted to hear from a developer who could actually tell us which one might be better and why. The following guest post is written by Josh Fraser, the co-founder of EventVue, who is an active contributor to PubSubHubbub in his free time. He has contributed several client libraries for PubSubHubbub including a WordPress plugin. Guess which side of the debate he falls on. In the past few months, a lot of attention has been given to the rise of the real-time web. The problem is that the web wasn't designed with real-time in mind. There is a huge need for the tech community to get behind new protocols that will power this fundamental shift in how web applications work. Today I want to take a look at two of the leading protocols that enable real-time notifications on the web. While there are older protocols that enable real-time notifications like XEP-0060, PubSubHubbub (PuSH) and rssCloud are two new protocols which show a lot of promise of gaining adoption. Both PuSH and rssCloud address a fundamental flaw in the way web applications work today. Currently, getting updates on the web requires constant polling. Subscribers are forced to act like nagging children asking, "Are we there yet?" Subscribers must constantly ping the publisher to ask if there are new updates even if the answer is "no" 99% of the time. This is terribly inefficient, wastes resources, and makes it incredibly hard to find new content in as soon as it appears. Both protocols flip the current model on its head so that updates are event driven rather than request driven. By that I mean that both protocols eliminate the need for polling by essentially telling subscribers, "Don't ask us if there's anything new. We'll tell you." But if you find yourself confused about how they are different, you're not alone.