<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Performance - Tag - vo.rs</title><link>https://vo.rs/tags/performance/</link><description>Performance - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 08 Sep 2025 10:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/performance/" rel="self" type="application/rss+xml"/><item><title>Kubernetes Resource Requests and Limits: The Difference Between Crashing and Thriving</title><link>https://vo.rs/story/kubernetes-resource-requests-and-limits-the-difference-between-crashing-and-thriving/</link><description>&lt;p&gt;Most Kubernetes pain that gets blamed on &amp;ldquo;the cluster being flaky&amp;rdquo; is actually a
resource-management problem. A pod that vanishes at 3am, a service that goes
sluggish under load for no obvious reason, a node that grinds to a halt — nine
times out of ten the root cause is a &lt;code&gt;requests&lt;/code&gt; value someone copied from a
tutorial and a &lt;code&gt;limits&lt;/code&gt; value nobody thought about. So let me walk through how
this actually works, because the scheduler&amp;rsquo;s behaviour is not intuitive until
you&amp;rsquo;ve been burned by it.&lt;/p&gt;</description><pubDate>Mon, 08 Sep 2025 10:00:00 +0000</pubDate></item></channel></rss>