<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pet Projects on Alexey Panfilov — Product, AI, Systems</title><link>https://dzarlax.dev/tags/pet-projects/</link><description>Recent content in Pet Projects on Alexey Panfilov — Product, AI, Systems</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://dzarlax.dev/tags/pet-projects/index.xml" rel="self" type="application/rss+xml"/><item><title>Trading a 1.3 GB Bookmark Manager for 17 MB</title><link>https://dzarlax.dev/articles/trading-a-1.3-gb-bookmark-manager-for-17-mb/</link><pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate><guid>https://dzarlax.dev/articles/trading-a-1.3-gb-bookmark-manager-for-17-mb/</guid><description>&lt;p&gt;I had been ignoring it for a while: every time I looked at &lt;code&gt;docker stats&lt;/code&gt; on my Hetzner VPS, Karakeep was the heaviest container by a wide margin. A 7.6 GB box, 25 services, and one Node app taking &lt;strong&gt;1.32 GB&lt;/strong&gt; of resident memory for what is, in my use, a glorified link list with screenshots.&lt;/p&gt;
&lt;p&gt;Available RAM had drifted down to &lt;strong&gt;1.4 GB&lt;/strong&gt;, swap was pinned at 2.0 / 2.0 GB, and Postgres (capped at 768 MB) was hitting 61% utilisation. Nothing was on fire, but the margin had stopped feeling like a margin.&lt;/p&gt;</description></item></channel></rss>