<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>LLMOps on Eugeniusz Zabłocki Blog</title>
    <link>https://ezablocki.com/tags/llmops/</link>
    <description>Recent content in LLMOps on Eugeniusz Zabłocki Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© Eugeniusz Zabłocki</copyright>
    <lastBuildDate>Mon, 18 May 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://ezablocki.com/tags/llmops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Smashing the O(N) Bottleneck: Horizontal Scaling and State Isolation in LangGraph</title>
      <link>https://ezablocki.com/posts/sentinel-ai-part-1-map-reduce/</link>
      <pubDate>Mon, 18 May 2026 10:00:00 +0200</pubDate>
      
      <guid>https://ezablocki.com/posts/sentinel-ai-part-1-map-reduce/</guid>
      <description>If you’ve ever built a prototype of an LLM agent, you probably started with a clean, sequential flow. A user inputs a file, your agent processes it item by item in a standard Python loop, and returns a response. It works beautifully on your local machine with three test cases.
Then, you hit production.
Suddenly, a user uploads a manifest file with 60 dependencies. Processing them sequentially means your application locks up, the latency spikes linearly, and your time-to-first-token (TTFT) degrades into minutes.</description>
    </item>
    
  </channel>
</rss>
