<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Page-Cache on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/page-cache/</link>
    <description>Recent content in Page-Cache on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/page-cache/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Page Cache Inspection: pcstat vs vmtouch vs fincore — Self-Hosted Filesystem Cache Management</title>
      <link>https://www.pistack.xyz/posts/2026-05-23-linux-page-cache-inspection-pcstat-vmtouch-fincore-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-23-linux-page-cache-inspection-pcstat-vmtouch-fincore-guide/</guid>
      <description>&lt;p&gt;The Linux page cache is one of the most powerful performance optimizations built into the kernel — it automatically caches recently accessed file data in unused RAM, dramatically accelerating repeat reads without any application changes. But this invisible caching layer can also mask memory pressure, cause confusion about &amp;ldquo;missing&amp;rdquo; RAM, and lead to suboptimal I/O patterns when hot data gets evicted. Three tools help administrators inspect and manage the page cache: &lt;strong&gt;pcstat&lt;/strong&gt; (page cache statistics), &lt;strong&gt;vmtouch&lt;/strong&gt; (virtual memory touch), and &lt;strong&gt;fincore&lt;/strong&gt; (file in-core). Understanding which files are cached, how much memory they consume, and how to control caching behavior is essential for tuning self-hosted server performance.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
