<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pressure Stall Information on Netdata</title><link>https://www.netdata.cloud/tags/pressure-stall-information/</link><description>Recent content in Pressure Stall Information on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 05:09:03 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/pressure-stall-information/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux Cgroups V2 Memory Throttling &amp; OOM Fix</title><link>https://www.netdata.cloud/academy/diagnosing-linux-cgroups/</link><pubDate>Fri, 05 Sep 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/academy/diagnosing-linux-cgroups/</guid><description>&lt;p&gt;Your critical service is lagging. Users are complaining about timeouts. You check your orchestration platform and see the dreaded &lt;code&gt;OOMKilled&lt;/code&gt; status on a container. You dive into the node&amp;rsquo;s logs (&lt;code&gt;dmesg&lt;/code&gt;) and confirm it: the kernel&amp;rsquo;s Out-of-Memory (OOM) killer has claimed another victim. The immediate fix is easy—restart the container, maybe give it more memory—but the real question remains unanswered: &lt;em&gt;why&lt;/em&gt; did it happen? Was it a sudden memory leak, a traffic spike, or something more subtle?&lt;/p&gt;</description></item><item><title>Linux Load Average Myths and Realities</title><link>https://www.netdata.cloud/blog/linux-load-average-myths-and-realities/</link><pubDate>Sun, 03 Nov 2024 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/linux-load-average-myths-and-realities/</guid><description>&lt;p&gt;When it comes to monitoring system &lt;a href="https://www.netdata.cloud/solutions/technologies/linux-monitoring/"&gt;performance on Linux&lt;/a&gt;, the load average is one of the most referenced metrics. Displayed prominently in tools like &lt;code&gt;top&lt;/code&gt;, &lt;code&gt;uptime&lt;/code&gt;, and &lt;code&gt;htop&lt;/code&gt;, it&amp;rsquo;s often used as a quick gauge of system load and capacity. But how reliable is it? For complex, multi-threaded applications, load average can paint a misleading picture of actual system performance.&lt;/p&gt;&#10;&lt;p&gt;In this article, we&amp;rsquo;ll dive into the myths and realities of Linux load average, using insights from Netdata’s high-frequency, high-concurrency monitoring setup. Through this journey, we&amp;rsquo;ll uncover why load average spikes can occur even under steady workloads, and why a single metric is rarely enough to capture the true state of a system. Whether you&amp;rsquo;re a system administrator, developer, or performance enthusiast, this exploration of load average will help you interpret it more accurately and understand when it may—or may not—reflect reality.&lt;/p&gt;</description></item><item><title>Linux CPU Consumption, Load &amp; Pressure Explained</title><link>https://www.netdata.cloud/blog/understanding-linux-cpu-consumption-load-and-pressure-for-performance-optimisation/</link><pubDate>Tue, 02 May 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/understanding-linux-cpu-consumption-load-and-pressure-for-performance-optimisation/</guid><description>&lt;p&gt;&lt;img src="../2023-05-02-understanding-linux-cpu-consumption-load-and-pressure-for-performance-optimisation/img/stacked-netdata.png" alt="stacked-netdata"&gt;&lt;/p&gt;&#10;&lt;p&gt;As a system administrator, understanding how your Linux system&amp;rsquo;s CPU is being utilized is crucial for identifying bottlenecks and &lt;a href="https://www.netdata.cloud/academy/what-is-cardinality-in-databases-a-comprehensive-guide/"&gt;optimizing performance&lt;/a&gt;. In this blog post, we&amp;rsquo;ll dive deep into the world of Linux CPU consumption, load, and pressure, and discuss how to use these metrics effectively to identify issues and improve your system&amp;rsquo;s performance.&lt;/p&gt;&#10;&lt;!-- truncate --&gt;&#10;&lt;h2 id="cpu-consumption-and-utilization"&gt;CPU Consumption and Utilization&lt;/h2&gt;&#10;&lt;p&gt;CPU consumption refers to the amount of processing power being used by applications running on your system. The &lt;code&gt;system.cpu&lt;/code&gt; chart in Netdata represents the Total CPU utilization of your Linux system, broken down into different dimensions. Each dimension provides insight into how the CPU is being used by various tasks and processes. Here&amp;rsquo;s a brief explanation of each dimension:&lt;/p&gt;</description></item><item><title>Kubernetes node CPU saturation: load, throttling, and runqueue depth</title><link>https://www.netdata.cloud/guides/kubernetes/kubernetes-node-cpu-saturation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/guides/kubernetes/kubernetes-node-cpu-saturation/</guid><description>&lt;p&gt;Application latency climbs and pods slow down. &lt;code&gt;kubectl top nodes&lt;/code&gt; reports 70 percent CPU, so you assume headroom exists. It does not. CPU percent is a time-average that masks micro-bursts, runqueue backlog, and CFS throttling. A container can throttle to a crawl while node utilization looks comfortable, and a node can show 50 percent utilization with every runnable thread queued behind a noisy neighbor. Distinguish node-level CPU contention from limit-induced throttling using runqueue depth, CFS bandwidth metrics, and Pressure Stall Information (PSI).&lt;/p&gt;</description></item></channel></rss>