<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Transfer on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/transfer/</link><description>Recent content in Transfer 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/transfer/index.xml" rel="self" type="application/rss+xml"/><item><title>Optimizing ML Tensor Storage and Transfer</title><link>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/project-optimizing-ml-tensor-storage/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/project-optimizing-ml-tensor-storage/</guid><description>&lt;h2 id="optimizing-ml-tensor-storage-and-transfer"&gt;Optimizing ML Tensor Storage and Transfer&lt;/h2&gt;
&lt;p&gt;Welcome back, future data compression wizard! In this chapter, we&amp;rsquo;re diving into one of the most exciting and impactful applications of OpenZL: &lt;strong&gt;optimizing the storage and transfer of Machine Learning (ML) tensors.&lt;/strong&gt; If you&amp;rsquo;ve ever worked with large ML models, you know that tensors – the multi-dimensional arrays that represent everything from model weights to activation maps – can become incredibly bulky. This bulk leads to slow loading times, high storage costs, and bottlenecks in data transfer, especially in distributed training or inference scenarios.&lt;/p&gt;</description></item></channel></rss>