<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Benchmark on LoopGain Blog</title>
    <link>https://loopgain.ai/blog/tags/benchmark/</link>
    <description>Recent content in Benchmark on LoopGain Blog</description>
    <image>
      <title>LoopGain Blog</title>
      <url>https://loopgain.ai/blog/og-default.png</url>
      <link>https://loopgain.ai/blog/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 12 Jun 2026 09:00:00 -0400</lastBuildDate>
    <atom:link href="https://loopgain.ai/blog/tags/benchmark/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>We instrumented 90 &#39;fix until green&#39; agent loops. Here&#39;s what they waste.</title>
      <link>https://loopgain.ai/blog/posts/we-instrumented-90-agent-loops/</link>
      <pubDate>Fri, 12 Jun 2026 09:00:00 -0400</pubDate>
      <guid>https://loopgain.ai/blog/posts/we-instrumented-90-agent-loops/</guid>
      <description>Everyone is running agents in overnight loops now. We put a convergence monitor on 90 real ones — every iteration a full headless agent session spending real API dollars — and measured whether the math holds at session scale, where a governed stop actually saves money, and the honest bug we found in our own stop rule.</description>
    </item>
    <item>
      <title>We ran 2,000 paired agent-loop trials. Here&#39;s what surprised us.</title>
      <link>https://loopgain.ai/blog/posts/2000-agent-loop-trials-what-surprised-us/</link>
      <pubDate>Sun, 07 Jun 2026 09:05:00 -0400</pubDate>
      <guid>https://loopgain.ai/blog/posts/2000-agent-loop-trials-what-surprised-us/</guid>
      <description>A pre-registered benchmark of LoopGain vs fixed max_iterations across 2,000 paired trials and six agent frameworks. The headline is 92.8% cheaper — but the interesting findings are the five things that complicate it.</description>
    </item>
  </channel>
</rss>
