<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="http://acousma.page/feed.xml" rel="self" type="application/atom+xml" /><link href="http://acousma.page/" rel="alternate" type="text/html" /><updated>2026-09-20T18:16:34+00:00</updated><id>http://acousma.page/feed.xml</id><subtitle></subtitle><entry><title type="html">A Learning Map for Reinforcement Learning Infrastructure</title><link href="http://acousma.page/reinforcement-learning/infrastructure/2026/07/03/rl-infrastructure-learning-map.html" rel="alternate" type="text/html" title="A Learning Map for Reinforcement Learning Infrastructure" /><published>2026-07-03T20:00:00+00:00</published><updated>2026-07-03T20:00:00+00:00</updated><id>http://acousma.page/reinforcement-learning/infrastructure/2026/07/03/rl-infrastructure-learning-map</id><content type="html" xml:base="http://acousma.page/reinforcement-learning/infrastructure/2026/07/03/rl-infrastructure-learning-map.html"><![CDATA[<p>Reinforcement learning infrastructure connects several systems that are often studied separately: model training, inference, data generation, reward computation, scheduling, and distributed execution.</p>

<p>A useful learning order is:</p>

<ol>
  <li>Understand the algorithmic loop: rollout, reward, advantage estimation, and policy update.</li>
  <li>Map each stage to its system requirements.</li>
  <li>Identify where models and data move between training and inference engines.</li>
  <li>Study synchronization, staleness, batching, and resource allocation.</li>
  <li>Measure end-to-end throughput instead of optimizing one stage in isolation.</li>
</ol>

<p>The most important systems question is usually not “Which component is slow?” It is:</p>

<blockquote>
  <p>Which bottleneck currently limits the rate at which useful training samples become policy updates?</p>
</blockquote>

<p>That framing makes it easier to reason about asynchronous execution, reward-model capacity, rollout scheduling, and GPU allocation.</p>]]></content><author><name></name></author><category term="reinforcement-learning" /><category term="infrastructure" /><summary type="html"><![CDATA[Reinforcement learning infrastructure connects several systems that are often studied separately: model training, inference, data generation, reward computation, scheduling, and distributed execution.]]></summary></entry><entry><title type="html">Why I Started This Blog</title><link href="http://acousma.page/career/ml-systems/2026/07/03/welcome.html" rel="alternate" type="text/html" title="Why I Started This Blog" /><published>2026-07-03T19:00:00+00:00</published><updated>2026-07-03T19:00:00+00:00</updated><id>http://acousma.page/career/ml-systems/2026/07/03/welcome</id><content type="html" xml:base="http://acousma.page/career/ml-systems/2026/07/03/welcome.html"><![CDATA[<p>I started this blog to turn scattered learning into reusable knowledge.</p>

<p>My work and interests sit at the intersection of machine learning systems, distributed training, GPU performance, and reinforcement learning infrastructure. These topics are often explained either too abstractly or with too much implementation detail. I want to write explanations that connect the underlying ideas to practical engineering decisions.</p>

<p>I also want this blog to serve as a record of growth: what I learned, what assumptions changed, and how I approach difficult infrastructure problems.</p>

<p>Topics I plan to write about include:</p>

<ul>
  <li>How to reason about GPU bottlenecks</li>
  <li>Distributed training trade-offs</li>
  <li>Training and inference systems</li>
  <li>Reinforcement learning infrastructure</li>
  <li>Compiler and kernel optimization</li>
  <li>Lessons from building reliable ML platforms</li>
</ul>

<p>Everything here reflects my personal views and uses only information that is appropriate to share publicly.</p>]]></content><author><name></name></author><category term="career" /><category term="ml-systems" /><summary type="html"><![CDATA[I started this blog to turn scattered learning into reusable knowledge.]]></summary></entry></feed>