<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>system-design on toorun.dev</title><link>https://toorun.dev/tags/system-design/</link><description>Recent content in system-design on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 08 Sep 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Embedded Linux RAM Requirements: How Much Memory Does Your System Really Need?</title><link>https://toorun.dev/posts/embedded-linux-ram-requirements-how-much-memory-does-your-system-really-need/</link><pubDate>Tue, 08 Sep 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/embedded-linux-ram-requirements-how-much-memory-does-your-system-really-need/</guid><description>Embedded Linux RAM Requirements: How Much Memory Does Your System Really Need? If you are designing an embedded Linux product, the big mistake is treating RAM as a binary choice: either “Linux runs” or “Linux does not run.” In practice, the right question is: what does your product actually do, and how much memory does that workload need?
A system can boot with 32 MB, but a product with a UI, networking, and a package-based filesystem often needs much more.</description></item></channel></rss>