<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Chris&#x27; Externalized Inner Monologue - nfs</title>
    <link rel="self" type="application/atom+xml" href="https://chris.ortner-moises.com/tags/nfs/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://chris.ortner-moises.com"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-03-18T00:00:00+00:00</updated>
    <id>https://chris.ortner-moises.com/tags/nfs/atom.xml</id>
    <entry xml:lang="en">
        <title>NFS performance troubles</title>
        <published>2026-03-18T00:00:00+00:00</published>
        <updated>2026-03-18T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Chris Ortner-Moises
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://chris.ortner-moises.com/writing/nfs-performance/"/>
        <id>https://chris.ortner-moises.com/writing/nfs-performance/</id>
        
        <summary type="html">&lt;p&gt;Recently, I started having issues with self-hosted services running slow, despite ample memory reserves and load averages that were fractions of the number of available CPUs.
That got pretty annoying, especially given that I recently set up Grafana alerts that send Telegram notifications when one of the services is slow or unreachable.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
