Blogs

How We Found 7 TiB of Memory Just Sitting Around

Render

How we saved 7 TiB of memory across our Kubernetes clusters by disabling namespace listwatching in Vector, reducing daemonset overhead and API server load at scale.

Visit Site

Blogs Render

BlogsNew compute plans for memory-intensive applicationsRender BlogsSo, You Want to Hire a UX Engineer?Render BlogsNew Region in Early Access: Virginia (US East)Render BlogsHeroku Changed EverythingRender Blogs...It Works Fine LocallyRender BlogsInfrastructure patterns for agentic applicationsRender BlogsHow NetEase Games achieved 30-second LLM cold starts on KubernetesCncf BlogsLovable’s OJ Rewrites Vite’s Dev Server in Rust as AI Lowers the Cost of Forking Open SourceSocket BlogsVite Releases Technical Preview of Rolldown-Vite, a Rust-Based BundlerSocket News3 Reasons In-Memory Computing Is Essential for MicroservicesThenewstack NewsData Persistence and Storage over Pancakes at KubeCon EU 2021Thenewstack NewsLooking Around Reliability Corners During a Kubernetes MigrationThenewstack BlogsJust Sharing My GulpfileCss Tricks BlogsWhat Makes a Great Dive? The DiveMaxxing WinnersMotherduck BlogsJust Released: Hybrid Query Processing Paper at CIDR 2024Motherduck ResourcesAccessible tap targetsWeb BlogsEveryone wants AI. That isn't enough.Notion So BlogsWe're Cutting L40S Prices In HalfFly BlogsUsing TurboStream with the Fetch APIFly BlogsDocker Desktop 4.22: Resource Saver, Compose ‘include’, and Enhanced RBAC FunctionalityDocker