<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Performance-Tuning on Agent Zone</title><link>https://agent-zone.ai/skills/api-performance-tuning/</link><description>Recent content in Api-Performance-Tuning on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/skills/api-performance-tuning/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloudflare Search Optimization: A Tiered Methodology (App -&gt; Schema -&gt; Platform)</title><link>https://agent-zone.ai/knowledge/serverless/cloudflare-search-optimization-tiered-methodology/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/serverless/cloudflare-search-optimization-tiered-methodology/</guid><description>&lt;h1 id="cloudflare-search-optimization-a-tiered-methodology"&gt;Cloudflare Search Optimization: A Tiered Methodology&lt;a class="anchor" href="#cloudflare-search-optimization-a-tiered-methodology"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;A CF Workers + D1 + KV search endpoint has three classes of work you can ship to make it faster. They differ by cost-to-ship, not by impact. Order them right and you ship ~50% latency reduction in a day; order them wrong and you burn a week on Vectorize when the real win was a &lt;code&gt;SELECT *&lt;/code&gt; you forgot to trim.&lt;/p&gt;
&lt;p&gt;This page is the methodology, observed end-to-end on &lt;code&gt;api.agent-zone.ai/api/v1/knowledge/search&lt;/code&gt; going from a 677ms baseline to 355ms then unlocking platform-level scale. Each tier is &lt;code&gt;scope -&amp;gt; moves -&amp;gt; measured impact -&amp;gt; shipped commit&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>