<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Benchmarking on API Coding</title>
    <link>https://apicoding.com/tags/benchmarking/</link>
    <description>Recent content in Benchmarking on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/benchmarking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Benchmarking MCP Servers and Stateful API Workflows: Latency, Throughput and Tokens per Call</title>
      <link>https://apicoding.com/benchmarking-mcp-servers-and-stateful-api-workflows-latency-throughput-and-tokens-per-call/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/benchmarking-mcp-servers-and-stateful-api-workflows-latency-throughput-and-tokens-per-call/</guid>
      <description>&lt;p&gt;Point wrk at an MCP server and you get a clean report: every response a 200. Some of those 200s carry &lt;code&gt;isError: true&lt;/code&gt; results, and nothing in the output says what the tool definitions cost the model on every turn. The tool is measuring requests per second. An agent runs a workflow, and what the server costs it is latency per call times calls per task, plus the tokens each response and each definition puts into its context.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
