<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on Besmir Zanaj</title><link>https://cloudalbania.com/tags/performance/</link><description>Recent content in Performance on Besmir Zanaj</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudalbania.com/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux performance troubleshooting: a quick checklist</title><link>https://cloudalbania.com/2026-10-linux-performance-troubleshooting/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><guid>https://cloudalbania.com/2026-10-linux-performance-troubleshooting/</guid><description>Why this list A server is slow, someone is waiting, and you have just logged in. It is tempting to start guessing. What I do instead is run a fixed set of commands that, in about a minute, tells me whether the problem is CPU, memory, disk or network, and where to look next.
This is the checklist I use, written for the junior and medior sysadmins I work with: what each command is for and the one or two things I look at in its output.</description></item></channel></rss>