<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: spinhire</title><link>https://news.ycombinator.com/user?id=spinhire</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 12 Sep 2026 14:12:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=spinhire" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by spinhire in "Show HN: We served 5k dynamic websites from a 2-vCPU, 4 GB VPS"]]></title><description><![CDATA[
<p>The admission that all 5,000 sites are identical clones matters more than it
looks. Identical content means one shared working set in the OS page cache, so
this mostly measures template rendering, not the memory behaviour of 5,000
different datasets — which is the thing that actually decides whether a small
box survives.
The number I'd stare at is p95 = 1.43s at 146 rps with CPU peaking at 81%.
That's the point where a small VPS stops being comfortably idle and becomes one
background job away from trouble. We run a much smaller site on a similar box,
and what breaks latency there has never been traffic — it's the crawler and
image generation competing for the same two cores.
Is that server serving only, or does it also run the background work for those
sites?</p>
]]></description><pubDate>Thu, 10 Sep 2026 22:42:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=49651113</link><dc:creator>spinhire</dc:creator><comments>https://news.ycombinator.com/item?id=49651113</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49651113</guid></item></channel></rss>