<?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>Linux on Sanketh's Blog</title><link>https://sankethbk.github.io/blog/tags/linux/</link><description>Recent content in Linux on Sanketh's Blog</description><generator>Hugo -- 0.167.0</generator><language>en-us</language><lastBuildDate>Sat, 03 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sankethbk.github.io/blog/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Performance Engineering: A Practical Starting Map</title><link>https://sankethbk.github.io/blog/posts/performance-engineering/2026-10-03-starting-map/</link><pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate><guid>https://sankethbk.github.io/blog/posts/performance-engineering/2026-10-03-starting-map/</guid><description>&lt;h1 id="performance-engineering-a-practical-starting-map"&gt;Performance Engineering: A Practical Starting Map&lt;/h1&gt;
&lt;p&gt;This is the first note in a performance-engineering sequence. It is not a summary of an SRE handbook, a cloud-observability guide, or a treatise on dashboard design. The goal is practical skill at the level of a single machine: understand why a program is slow, decide what to change, and verify that the change worked.&lt;/p&gt;
&lt;p&gt;The contexts that matter here are things like a chess engine, the microbenchmark problems on HFT University, a hot loop in the Linux kernel, or any single-node program where you own the source and the hardware. The operating system is the boundary we press against; the hardware is the ground truth.&lt;/p&gt;</description></item></channel></rss>