<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Efficiency on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/efficiency/</link><description>Recent content in Efficiency on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 26 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/efficiency/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction to JSON and TOON for AI</title><link>https://ai-blog.noorshomelab.dev/json-toon-for-ai-guide/introduction-to-json-toon-for-ai/</link><pubDate>Sat, 15 Nov 2025 03:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/json-toon-for-ai-guide/introduction-to-json-toon-for-ai/</guid><description>&lt;h1 id="introduction-to-json-and-toon-for-ai"&gt;Introduction to JSON and TOON for AI&lt;/h1&gt;
&lt;p&gt;Welcome to the exciting world of data formats optimized for Artificial Intelligence! In this introductory chapter, we&amp;rsquo;ll lay the groundwork for understanding JSON (JavaScript Object Notation) and TOON (Token-Oriented Object Notation), two critical formats for interacting with AI models, especially Large Language Models (LLMs). We&amp;rsquo;ll explore what they are, why they are so important in the AI landscape, and how to set up your development environment to start working with them.&lt;/p&gt;</description></item><item><title>Defining Data Schemas with OpenZL</title><link>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/defining-data-schemas-openzl/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/defining-data-schemas-openzl/</guid><description>&lt;h2 id="introduction-to-data-schemas-in-openzl"&gt;Introduction to Data Schemas in OpenZL&lt;/h2&gt;
&lt;p&gt;Welcome back, future compression wizard! In our previous chapters, we introduced OpenZL as a revolutionary, format-aware compression framework. We learned that unlike traditional compressors that treat data as a generic byte stream, OpenZL thrives on understanding the &lt;em&gt;structure&lt;/em&gt; of your data. But how exactly do we tell OpenZL what our data looks like? That&amp;rsquo;s precisely what this chapter is all about!&lt;/p&gt;
&lt;p&gt;Here, we&amp;rsquo;ll dive deep into defining data schemas with OpenZL. You&amp;rsquo;ll learn why describing your data&amp;rsquo;s structure is paramount for OpenZL&amp;rsquo;s efficiency, explore the core concepts behind this &amp;ldquo;data description,&amp;rdquo; and walk through practical examples to build your first OpenZL-compatible schema. Get ready to unlock the true power of structured data compression!&lt;/p&gt;</description></item><item><title>Crafting Custom Codecs for Unique Data</title><link>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/crafting-custom-codecs/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/crafting-custom-codecs/</guid><description>&lt;h2 id="crafting-custom-codecs-for-unique-data"&gt;Crafting Custom Codecs for Unique Data&lt;/h2&gt;
&lt;p&gt;Welcome back, compression enthusiast! In the previous chapters, we explored OpenZL&amp;rsquo;s foundational concepts and got our environment set up. You&amp;rsquo;re now familiar with how OpenZL leverages its modular architecture for efficient data compression. But what if your data isn&amp;rsquo;t a &amp;ldquo;standard&amp;rdquo; type? What if it has a unique structure that off-the-shelf compressors just can&amp;rsquo;t handle optimally?&lt;/p&gt;
&lt;p&gt;This chapter is where OpenZL truly shines. We&amp;rsquo;re going to dive into the powerful concept of &amp;ldquo;crafting custom codecs.&amp;rdquo; Don&amp;rsquo;t worry, you won&amp;rsquo;t be writing complex C++ compression algorithms from scratch. Instead, you&amp;rsquo;ll learn how to &lt;em&gt;describe your data&amp;rsquo;s unique structure&lt;/em&gt; to OpenZL, allowing it to intelligently &lt;em&gt;generate&lt;/em&gt; or &lt;em&gt;configure&lt;/em&gt; a highly optimized compression plan—effectively a custom codec tailored just for your data. This &amp;ldquo;format-aware&amp;rdquo; approach is a game-changer for specialized datasets like time-series, machine learning tensors, and complex database records.&lt;/p&gt;</description></item><item><title>Lean &amp;amp; Mean - Dockerfile Best Practices for Efficiency</title><link>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-08-dockerfile-best-practices/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/docker-mastery-2025/chapter-08-dockerfile-best-practices/</guid><description>&lt;h2 id="lean--mean---dockerfile-best-practices-for-efficiency"&gt;Lean &amp;amp; Mean - Dockerfile Best Practices for Efficiency&lt;/h2&gt;
&lt;h3 id="introduction"&gt;Introduction&lt;/h3&gt;
&lt;p&gt;Welcome back, future Docker masters! In our previous chapters, you&amp;rsquo;ve learned the fundamentals of Docker, how to build images with &lt;code&gt;docker build&lt;/code&gt;, and how to run containers with &lt;code&gt;docker run&lt;/code&gt;. You&amp;rsquo;ve even dabbled with creating your own Dockerfiles. That&amp;rsquo;s fantastic!&lt;/p&gt;
&lt;p&gt;But here&amp;rsquo;s a little secret: just because a Dockerfile &lt;em&gt;works&lt;/em&gt;, doesn&amp;rsquo;t mean it&amp;rsquo;s &lt;em&gt;good&lt;/em&gt;. As you move towards building applications for production, efficiency becomes paramount. Think about it: every megabyte in your Docker image takes longer to build, longer to push to a registry, longer to pull, and consumes more disk space and memory. A bloated image can slow down your entire development and deployment pipeline.&lt;/p&gt;</description></item><item><title>Parallel Compression and Distributed Systems</title><link>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/parallel-compression-distributed-systems/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/parallel-compression-distributed-systems/</guid><description>&lt;h2 id="introduction-to-parallel-compression-and-distributed-systems-with-openzl"&gt;Introduction to Parallel Compression and Distributed Systems with OpenZL&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid data explorer! In our journey through the fascinating world of OpenZL, we&amp;rsquo;ve learned how to craft intelligent compression plans and apply them to various data formats. But what happens when your data isn&amp;rsquo;t just large, but &lt;em&gt;enormous&lt;/em&gt;? What if it resides across many machines in a vast data lake? That&amp;rsquo;s where the power of parallel compression and distributed systems comes into play.&lt;/p&gt;</description></item><item><title>Subnetting: The Art of Not Letting Your Network Become a Hairball, According to Me, a Genius</title><link>https://ai-blog.noorshomelab.dev/blog/subnetting-networking-dumb-dumber-guide/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/blog/subnetting-networking-dumb-dumber-guide/</guid><description>&lt;p&gt;&amp;ldquo;Psst, hey! You smell that? Smells like&amp;hellip; &lt;em&gt;opportunity&lt;/em&gt;! And maybe a little bit like a network that’s about to go kablooey because someone forgot to use their head. But don&amp;rsquo;t you worry, pal, because &lt;em&gt;I&lt;/em&gt; am here to save the day!&amp;rdquo;&lt;/p&gt;
&lt;p&gt;(Pulls out a marker, draws a crude diagram of a tangled spaghetti monster on a napkin.)&lt;/p&gt;
&lt;p&gt;&amp;ldquo;See this? This is what your network looks like without subnetting. A big, dumb, delicious mess. And you know what they say about big dumb messes, right? They don&amp;rsquo;t get much done. Except maybe trip over their own feet. Constantly.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Chapter 4: Building Custom Docker Images with Dockerfiles</title><link>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-4-building-custom-docker-images-with-dockerfiles/</link><pubDate>Sun, 23 Nov 2025 22:00:12 +0530</pubDate><guid>https://ai-blog.noorshomelab.dev/a-complete-beginner-to-advanced-guide-on-docker-engine-29-0-2/chapter-4-building-custom-docker-images-with-dockerfiles/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the previous chapters, we learned how to run containers from existing Docker images. While readily available images from Docker Hub or private registries are incredibly useful, real-world applications often require specific configurations, custom code, or unique dependencies that aren&amp;rsquo;t met by generic images. This is where building your own custom Docker images becomes essential.&lt;/p&gt;
&lt;p&gt;Custom Docker images allow you to package your application and its entire environment into a portable, reproducible unit. The blueprint for creating these images is a &lt;code&gt;Dockerfile&lt;/code&gt;. A Dockerfile is a simple text file that contains a series of instructions that Docker Engine reads to build an image automatically. By mastering Dockerfiles, you gain precise control over your application&amp;rsquo;s deployment environment, ensuring consistency from development to production.&lt;/p&gt;</description></item></channel></rss>