<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Capacity-Planning on Luther Monson</title>
    <link>https://luth.io/tags/capacity-planning/</link>
    <description>Recent content in Capacity-Planning on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 25 Aug 2026 20:20:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/capacity-planning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Does One More WordPress Site Cost?</title>
      <link>https://luth.io/blog/2026/08/what-does-one-more-wordpress-site-cost/</link>
      <pubDate>Tue, 25 Aug 2026 20:20:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/08/what-does-one-more-wordpress-site-cost/</guid>
      <description>&lt;p&gt;ePHPm v0.7.0 shipped per-site multi-tenancy. Point &lt;code&gt;[server] sites_dir&lt;/code&gt; at a directory and every &lt;code&gt;Host&lt;/code&gt; maps to its own&#xA;docroot and its own Turso database file. One process serves all of them. The first question anybody asks about that is&#xA;&amp;ldquo;how many sites fit on a box?&amp;rdquo; The honest way to answer it is to turn the question around. What does &lt;strong&gt;one more&lt;/strong&gt; site&#xA;cost? If you know the marginal RAM, file descriptors, CPU and disk for a tenant, the box size falls out of arithmetic.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
