<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cpu_usage on Linux Café</title>
    <link>https://mrtomlinux.org/tags/cpu_usage/</link>
    <description>Recent content in Cpu_usage on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 17 May 2026 10:15:48 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/cpu_usage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming CPU Usage Spikes with `systemd` and `ps` in My Home Server Setup</title>
      <link>https://mrtomlinux.org/post/2026-05-17-taming-cpu-usage-spikes-with-systemd-and-ps-i/</link>
      <pubDate>Sun, 17 May 2026 10:15:48 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-17-taming-cpu-usage-spikes-with-systemd-and-ps-i/</guid>
      <description>&lt;h2 id=&#34;introduction-to-cpu-usage-spikes&#34;&gt;Introduction to CPU Usage Spikes&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve had my fair share of CPU usage spikes on my home server, and I&amp;rsquo;ve learned that they can be caused by a variety of factors, including resource-intensive applications, misconfigured services, or even malware. The real trick is to identify the root cause of the spike and take corrective action. In my experience, using &lt;code&gt;systemd&lt;/code&gt; and &lt;code&gt;ps&lt;/code&gt; can be a powerful way to manage CPU usage spikes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
