<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet href="https://rss.buzzsprout.com/styles.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:podcast="https://podcastindex.org/namespace/1.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:psc="http://podlove.org/simple-chapters" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <atom:link href="https://rss.buzzsprout.com/2618901.rss" rel="self" type="application/rss+xml" />
  <atom:link href="https://pubsubhubbub.appspot.com/" rel="hub" xmlns="http://www.w3.org/2005/Atom" />
  <title>Vanimal&#39;s Audio Blog</title>

  <lastBuildDate>Tue, 19 May 2026 13:27:44 -0400</lastBuildDate>
  <link>https://vanimalsaudioblog.buzzsprout.com</link>
  <language>en-us</language>
  <copyright>© 2026 Vanimal&#39;s Audio Blog</copyright>
  <podcast:locked>yes</podcast:locked>
    <podcast:guid>efa65d78-466f-5426-ba1b-d9074afffbde</podcast:guid>
  <podcast:txt purpose="verify">vanimal@vanimal.ai</podcast:txt>
  <itunes:author>Vanimal</itunes:author>
  <itunes:type>episodic</itunes:type>
  <itunes:explicit>false</itunes:explicit>
  <description><![CDATA[<p>Technology for the not so faint of heart. Now in your ears.<br><br></p><p>Most technology content is written for people who have time to read it. This is for everyone else.<br>Vanimal's Audio Blog delivers deep-dive commentary on AI infrastructure, enterprise storage, GPU compute, and the architecture decisions that define how modern organizations operate at scale. Each episode is drawn directly from the written work at vanimal.ai and produced for the way technical professionals actually consume content today: in the car, between meetings, or anywhere a screen is not the right tool.<br><br></p><p>The voice behind it is Van Flowers, known professionally as The Vanimal, a Senior Solutions Architect with 33 years of enterprise IT experience spanning data centers, global networks, and AI infrastructure. The content does not oversimplify. It treats you like someone who understands systems, tradeoffs, and why the details matter.<br><br></p><p>If you have ever wanted the infrastructure conversation without the slide deck, Vanimal's Audio Blog is the feed.<br><br></p><p>Subscribe, listen, and feel free to disagree.<br><br></p>]]></description>
  <generator>Buzzsprout (https://www.buzzsprout.com)</generator>
  <itunes:owner>
    <itunes:name>Vanimal</itunes:name>
    <itunes:email>vanimal@vanimal.ai</itunes:email>
  </itunes:owner>
  <image>
     <url>https://storage.buzzsprout.com/tnubkufvaodont0y0bgkpbz3ec0m?.jpg</url>
     <title>Vanimal&#39;s Audio Blog</title>
     <link></link>
  </image>
  <itunes:image href="https://storage.buzzsprout.com/tnubkufvaodont0y0bgkpbz3ec0m?.jpg" />
  <itunes:category text="Technology" />
  <item>
    <itunes:title>Why RDMA Changes Everything</itunes:title>
    <title>Why RDMA Changes Everything</title>
    <itunes:summary><![CDATA[RDMA does not optimize your infrastructure. It redesigns it.   Most organizations are still running AI inference, backup jobs, and object storage access over a CPU-mediated network stack that was never built for this workload density. Every transaction burns kernel cycles. Every burst of concurrent I/O introduces latency variance that compounds at scale.   Remote Direct Memory Access removes the CPU from the data path entirely. Your GPUs get their data. Your backup windows compress. Your obje...]]></itunes:summary>
    <description><![CDATA[<p>RDMA does not optimize your infrastructure. It redesigns it.<br/><br/></p><p>Most organizations are still running AI inference, backup jobs, and object storage access over a CPU-mediated network stack that was never built for this workload density. Every transaction burns kernel cycles. Every burst of concurrent I/O introduces latency variance that compounds at scale.<br/><br/></p><p>Remote Direct Memory Access removes the CPU from the data path entirely. Your GPUs get their data. Your backup windows compress. Your object storage performs under mixed load without the usual surprises. The network finally gets out of the way.<br/><br/></p><p>I wrote a deep dive covering why RDMA direct and RDMA over S3 are game-changing across AI inference, data protection, and day-to-day storage operations, and what you need to get the architecture right from the start.</p><p>This is the FULL Audio reading of that Blog Post<br/><br/></p><p><b>Copyright    Vanimal.AI   2026 </b></p><p><a href='https://www.vanimal.ai'>www.vanimal.ai</a></p>]]></description>
    <content:encoded><![CDATA[<p>RDMA does not optimize your infrastructure. It redesigns it.<br/><br/></p><p>Most organizations are still running AI inference, backup jobs, and object storage access over a CPU-mediated network stack that was never built for this workload density. Every transaction burns kernel cycles. Every burst of concurrent I/O introduces latency variance that compounds at scale.<br/><br/></p><p>Remote Direct Memory Access removes the CPU from the data path entirely. Your GPUs get their data. Your backup windows compress. Your object storage performs under mixed load without the usual surprises. The network finally gets out of the way.<br/><br/></p><p>I wrote a deep dive covering why RDMA direct and RDMA over S3 are game-changing across AI inference, data protection, and day-to-day storage operations, and what you need to get the architecture right from the start.</p><p>This is the FULL Audio reading of that Blog Post<br/><br/></p><p><b>Copyright    Vanimal.AI   2026 </b></p><p><a href='https://www.vanimal.ai'>www.vanimal.ai</a></p>]]></content:encoded>
    <enclosure url="https://www.buzzsprout.com/2618901/episodes/19203936-why-rdma-changes-everything.mp3" length="10372378" type="audio/mpeg" />
    <itunes:author>Vanimal</itunes:author>
    <guid isPermaLink="false">Buzzsprout-19203936</guid>
    <pubDate>Tue, 19 May 2026 13:00:00 -0400</pubDate>
    <itunes:duration>861</itunes:duration>
    <itunes:keywords></itunes:keywords>
    <itunes:season>1</itunes:season>
    <itunes:episode>1</itunes:episode>
    <itunes:episodeType>full</itunes:episodeType>
    <itunes:explicit>false</itunes:explicit>
  </item>
</channel>
</rss>
