<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resource Management on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/resource-management/</link><description>Recent content in Resource Management on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/resource-management/index.xml" rel="self" type="application/rss+xml"/><item><title>7. Build Processes, Scaling, and Resource Management</title><link>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/build-processes-scaling-resource-management/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/build-processes-scaling-resource-management/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future Void Cloud masters! In previous chapters, we learned how to get our projects up and running on Void Cloud, creating a seamless journey from local development to cloud deployment. But what happens &lt;em&gt;behind the scenes&lt;/em&gt; when you hit that &lt;code&gt;void deploy&lt;/code&gt; command? How does Void Cloud transform your source code into a live, responsive application? And how does it handle sudden spikes in user traffic without breaking a sweat?&lt;/p&gt;</description></item><item><title>Chapter 9: Resource Management and Performance Tuning</title><link>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/09-resource-management/</link><pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/apple-containers-mac-2026/09-resource-management/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 9! As you become more comfortable running Linux containers natively on your Mac using Apple&amp;rsquo;s &lt;code&gt;container&lt;/code&gt; tool, you&amp;rsquo;ll inevitably encounter situations where performance isn&amp;rsquo;t quite what you expect, or your Mac starts to feel sluggish. This is where resource management and performance tuning come into play.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll dive deep into understanding how your containers consume CPU, memory, and other system resources, and crucially, how to control these allocations using Apple&amp;rsquo;s &lt;code&gt;container&lt;/code&gt; CLI. We&amp;rsquo;ll explore practical ways to monitor container performance, identify bottlenecks, and apply tuning strategies to ensure your development environment is both efficient and stable. By the end of this chapter, you&amp;rsquo;ll have the skills to optimize your containerized applications, preventing them from hogging precious system resources and keeping your Mac running smoothly.&lt;/p&gt;</description></item><item><title>Securing Containers with Non-Root Users and Resource Limits</title><link>https://ai-blog.noorshomelab.dev/docker-compose-prod-stack-2026/securing-containers-non-root-users-resource-limits/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-compose-prod-stack-2026/securing-containers-non-root-users-resource-limits/</guid><description>&lt;p&gt;Running applications in production demands not just functionality but also robust security and stable performance. A common oversight in container deployments is operating services with excessive privileges or without proper resource constraints. This can turn a minor vulnerability into a critical system compromise or a simple traffic spike into a cascading outage.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll implement two fundamental production best practices for Docker containers: running services as non-root users and defining explicit CPU and memory limits. These measures significantly reduce your application&amp;rsquo;s attack surface and ensure predictable resource consumption, making your multi-service stack more resilient.&lt;/p&gt;</description></item><item><title>Context Managers and the `with` Statement</title><link>https://ai-blog.noorshomelab.dev/python-mastery-2025/chapter-13-context-managers-with-statement/</link><pubDate>Wed, 03 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/python-mastery-2025/chapter-13-context-managers-with-statement/</guid><description>&lt;h2 id="introduction-managing-resources-gracefully-with-with"&gt;Introduction: Managing Resources Gracefully with &lt;code&gt;with&lt;/code&gt;&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid coder! In this chapter, we&amp;rsquo;re going to unlock a powerful Python construct that makes managing resources super easy and safe: &lt;strong&gt;Context Managers&lt;/strong&gt; and the &lt;strong&gt;&lt;code&gt;with&lt;/code&gt; statement&lt;/strong&gt;. You&amp;rsquo;ll discover how these tools help you handle things like files, network connections, or database sessions without worrying about leaving them open or messy.&lt;/p&gt;
&lt;p&gt;Why does this matter? Imagine you open a file to write some data. What if your program crashes right in the middle? That file might not be properly closed, leading to corrupted data or wasted system resources. Context managers are like a built-in safety net, ensuring that certain &amp;ldquo;setup&amp;rdquo; actions are always followed by their corresponding &amp;ldquo;cleanup&amp;rdquo; actions, even if things go wrong.&lt;/p&gt;</description></item></channel></rss>