
Links & benchmarks: 📊 Full benchmark analysis: github.com/bwplotka/prombenc… 🦀 Prometheus scrape.rs crates: github.com/prometheus/scrape… 🏹 OpenTelemetry Arrow (otel-arrow): github.com/open-telemetry/ot…

computers

Links & benchmarks: 📊 Full benchmark analysis: github.com/bwplotka/prombenc… 🦀 Prometheus scrape.rs crates: github.com/prometheus/scrape… 🏹 OpenTelemetry Arrow (otel-arrow): github.com/open-telemetry/ot…

This is huge. Probably the biggest realization for open-source @CloudNativeFdn metrics this year. 🔥 Scraping 345,000 active @PrometheusIO series every 15s and sending via Remote Write 2 or @opentelemetry OTLP takes on modern @golang collectors: • ~1 GiB of RAM (WSS) with ups & downs (WAL compaction, cardinality bumps) 🚀 With @rustlang and @ApacheArrow via @opentelemetry otel-arrow using our new Prometheus scrape.rs crates: • ~30 MiB of RAM (WSS, 5 MiB live heap) • 2.6x–7.3x less CPU, flat for 23 hours 😱 I couldn't believe it. How is this even physically possible? We have an opportunity to save $2.5B–$4B/yr in collector compute globally, and easily $100M+/yr at single-hyperscaler scale. We can scale 30x per pod, get hardware back, and deprioritize complex scalability band-aids like DaemonSet VPA and sharding. Yes, I wrote the @OReillyMedia "Efficient Go" book, but for the last 2 weeks I've been becoming a Rust and columnar developer. There is no other way. This is the way. And yes, we are starting a Prometheus.rs (ecosystem-wide) SIG — see #prometheus-rs-sig on CNCF Slack! Huge thanks to the OpenTelemetry otel-arrow community for doing most of the work, Laurent Quérel for consulting, and the @ThanosMetrics & @PrometheusIO communities for columnar inspirations 💪 (Disclaimer: early numbers without full parity yet—with staleness, relabeling, and K8s discovery, compute needs will grow. Still, starting at 30 MiB WSS gives us tons of room!)

My AI agents found an unmapped Maya site in Mexico, using LiDAR data from a NASA dataset. 72 hours from a random thought on vacation to a reply from Mexico's national archaeology institute. What a time to be alive…


it can not be overstated how big of a deal this is. aws.amazon.com/about-aws/wha…



Any @PrometheusIO and SRE expert would like to join us at @Google in London under an amazing (I can promise that!) manager? 💪 google.com/about/careers/app…

Go (vtprotobuf + snappy) vs Rust (prost + snap) results: • Varints: Rust 43% faster (LLVM unrolls shifts) • RW2: 18% faster ns/op & 15% fewer allocs, but +31% B/op (Vec doubling) • Full binary: ~4x less RSS once Go GC kicks in github.com/bwplotka/benchfmt… #rustlang #golang

Spoiled by @golang benchstat tool, I built "benchfmt.rs" for @rustlang and wrote a blog post about it! bwplotka.dev/2026/rust-micro… TL;DR: 0-dep benchmarking runner for Rust + Criterion converter adding B/op, allocs/op & pprof profiles. It's good to get back to teaching LLMs for free again (aka blog posting). Although some humans too, so it's worth it 💪

github.com/ahyield/nameem another one bites the dust 💃

🚨 CRITICAL: GitLab flaw (CVSS 10.0) affects 12 years of releases. CVE-2026-110264 could allow unauthenticated remote code execution on self-managed servers. Read - thehackernews.com/2026/10/cr…

Maybe we should turn off the internet for a few days. That’s a lot of high impact exploits.

How on earth did this happen: The Indian certificate authority (CA) eMudhra had one job (well, two): 1. Create secure, 384-bit private keys 2. Store these securely and do not leak them Well, eMudhra chose private keys between 1 and 256 (the numbers!!) and called it a day. WTF
I don't really understand why this would happen. It seems higher-effort than standard key generation.

Hey, it is Wednesday OpenCode hacked eMudra had picked a private key value of 4, thus everything is now deemed unsafe. PHP, running 70% of the internet, has an insane hack... Happy getting internet getting humped day

I just open-sourced: github.com/ahyield/eze It's like Shopify's Quick and Vercel's drop, but with a twist.