<?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>Performance on Shubham Singh</title>
    <link>https://1shubham7.blog/tags/performance/</link>
    <description>Recent content in Performance on Shubham Singh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://1shubham7.blog/tags/performance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CPU Isn&#39;t a Thing, It&#39;s Time: Kubernetes Millicores Explained</title>
      <link>https://1shubham7.blog/millicores/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/millicores/</guid>
      <description>What a Kubernetes CPU value actually measures: CPU-seconds per second on one logical CPU. How a 250m limit becomes cpu.max 25000 100000 and a 100 ms throttle window, why a request is a weight and not a cap, and why 1000m is a hyperthread, not a core.</description>
    </item>
    
    <item>
      <title>Some Super Interesting Process Management Pointers</title>
      <link>https://1shubham7.blog/process-pointers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/process-pointers/</guid>
      <description>nice and renice set a CPU scheduling weight and nothing else: the OOM killer reads oom_score, not NI. Why a lower nice cannot lift a cgroup cpu.max quota and why -10 versus &#43;10 is a weight ratio of about 87 to 1 rather than 20 steps, what each field of top&amp;#39;s %Cpu(s) line means and why it is every logical CPU summed, and why 717 tasks with 4 running means 713 of them are asleep.</description>
    </item>
    
  </channel>
</rss>
