<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Linux on Hanh Pham's Blog</title><link>https://hanhpham.vercel.app/tags/linux/</link><description>Recent content in Linux on Hanh Pham's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Sep 2026 09:00:00 +0700</lastBuildDate><atom:link href="https://hanhpham.vercel.app/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>CFS Quota Throttling &amp; Silent OOMKills: The Fallacy of Kubernetes CPU Limits</title><link>https://hanhpham.vercel.app/posts/kubernetes-cfs-cpu-throttling-and-resource-limits/</link><pubDate>Mon, 28 Sep 2026 09:00:00 +0700</pubDate><guid>https://hanhpham.vercel.app/posts/kubernetes-cfs-cpu-throttling-and-resource-limits/</guid><description>Setting hard CPU limits on latency-sensitive microservices destroys p99 response times while average utilization appears deceptively low. Here is how Linux CFS quotas, Go GOMAXPROCS, and GOMEMLIMIT actually behave under load.</description></item></channel></rss>