<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Memory on Samuel Matildes - Knowledge Base</title><link>https://matildes.dev/tags/memory/</link><description>Recent content in Memory on Samuel Matildes - Knowledge Base</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 26 Oct 2026 12:27:57 +0000</lastBuildDate><atom:link href="https://matildes.dev/tags/memory/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Host Honcho on Kubernetes with LiteLLM, Redis, and GitHub Copilot</title><link>https://matildes.dev/ai/honcho-litellm-github-copilot/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://matildes.dev/ai/honcho-litellm-github-copilot/</guid><description>&lt;p&gt;&lt;i class="fas fa-brain" aria-hidden="true"&gt;&lt;/i&gt; A self-hosted memory service for Hermes, with LiteLLM as the model gateway and GitHub Copilot as an upstream provider.&lt;/p&gt;
&lt;div class="kb-callout kb-callout--warning"&gt;
 &lt;div class="kb-callout__title"&gt;
 &lt;i class="fas fa-triangle-exclamation" aria-hidden="true"&gt;&lt;/i&gt;
 &lt;span&gt;Illustrative configuration only&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="kb-callout__body"&gt;
 Every hostname, namespace, IP address, image version, model name, key and resource value in this guide is an &lt;strong&gt;example&lt;/strong&gt;. Do not paste it into a production cluster unchanged. Create your own secrets outside Git, verify the current upstream image and model names, and apply your own network, backup and update policies.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="architecture-at-a-glance"&gt;Architecture at a glance&lt;a class="td-heading-self-link" href="#architecture-at-a-glance" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;figure class="honcho-architecture"&gt;
 &lt;img src="architecture.svg" alt="Diagram showing the relationship between Hermes, Honcho, LiteLLM, Redis, PostgreSQL with pgvector, and LLM endpoints"&gt;
&lt;/figure&gt;
&lt;p&gt;The request path is deliberately split into specialised layers:&lt;/p&gt;</description></item><item><title>Before You Scale: Why Software Optimization Beats Hardware Every Time</title><link>https://matildes.dev/software-engineering/memory-optimization/</link><pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate><guid>https://matildes.dev/software-engineering/memory-optimization/</guid><description>&lt;p&gt;&lt;i class="fas fa-microchip" aria-hidden="true"&gt;&lt;/i&gt; Before You Scale: Why Software Optimization Beats Hardware Every Time&lt;/p&gt;
&lt;h2 id="summary"&gt;Summary&lt;a class="td-heading-self-link" href="#summary" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When your application crashes with an Out-of-Memory (OOM) error, the instinctive response is often: &amp;ldquo;Let&amp;rsquo;s add more RAM.&amp;rdquo; In the age of cloud computing where resources are just a slider away, this approach has become the default. But what if I told you that a 30-minute code investigation could reduce your memory usage by &lt;strong&gt;95%&lt;/strong&gt;—turning a 3GB memory spike into 150MB?&lt;/p&gt;</description></item><item><title>How to Benchmark Linux with Tux Toaster</title><link>https://matildes.dev/linux/admin/benchmarking-with-tuxtoaster/</link><pubDate>Fri, 17 Oct 2025 00:00:00 +0000</pubDate><guid>https://matildes.dev/linux/admin/benchmarking-with-tuxtoaster/</guid><description>&lt;p&gt;
 &lt;a href="https://github.com/samatild/tuxtoaster" target="_blank" rel="noopener"&gt;
 &lt;i class="fab fa-github" aria-hidden="true"&gt;&lt;/i&gt; GitHub
 &lt;/a&gt;
 &amp;nbsp;•&amp;nbsp;
 &lt;a href="https://pypi.org/project/tuxtoaster" target="_blank" rel="noopener"&gt;
 &lt;i class="fab fa-python" aria-hidden="true"&gt;&lt;/i&gt; PyPI
 &lt;/a&gt;
 &amp;nbsp;
&lt;/p&gt;
&lt;p&gt;&lt;i class="fas fa-tachometer-alt" aria-hidden="true"&gt;&lt;/i&gt; Benchmark smarter, not harder — with Tux Toaster.&lt;/p&gt;
&lt;h2 id="what-is-tux-toaster"&gt;What is Tux Toaster?&lt;a class="td-heading-self-link" href="#what-is-tux-toaster" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://github.com/samatild/tuxtoaster"&gt;&lt;code&gt;Tux Toaster&lt;/code&gt;&lt;/a&gt; is an all-in-one performance toolkit for Linux. It triggers various load tests (&amp;ldquo;toasters&amp;rdquo;) to help you evaluate the performance and stability of your system across CPU, memory, disk, and network. It offers an interactive terminal menu with multi-select support and clear, stoppable workloads.&lt;/p&gt;</description></item></channel></rss>