<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Arm on Linux Café</title>
    <link>https://mrtomlinux.org/tags/arm/</link>
    <description>Recent content in Arm on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 27 Oct 2026 11:15:20 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/arm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Diagnosing a 30‑second Nginx start‑up lag on an 8‑core ARM home‑server</title>
      <link>https://mrtomlinux.org/post/2026-10-27-diagnosing-a-30second-nginx-startup-lag-on-an/</link>
      <pubDate>Tue, 27 Oct 2026 11:15:20 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-10-27-diagnosing-a-30second-nginx-startup-lag-on-an/</guid>
      <description>&lt;h2 id=&#34;the-30second-nginx-startup-mystery-on-an-8core-arm-box&#34;&gt;The 30‑second Nginx start‑up mystery on an 8‑core ARM box&lt;/h2&gt;&#xA;&lt;p&gt;I had a clean 8‑core ARM server (Cortex‑A72, 4 GB RAM) running Debian 12. Nginx was the only service that took longer than a couple of seconds to come up. The log said “started” after 30 s, but the system was idle otherwise. I wanted to know why a stateless web server was so slow to boot on a modern CPU.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
