<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on Jamal Yusuf</title><link>https://jamal.dev/tags/performance/</link><description>Recent content in Performance on Jamal Yusuf</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jamal.dev/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Go Remains the Best Language for LLM Orchestration</title><link>https://jamal.dev/writing/go-llm-orchestration/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/go-llm-orchestration/</guid><description>&lt;p&gt;I have orchestrated LLM workloads in more than one language. Python gets you to demo fast. Go gets you to &lt;strong&gt;sleep&lt;/strong&gt; — or at least to on-call with fewer surprises.&lt;/p&gt;
&lt;p&gt;That is not ideology. It is fifteen years of distributed systems scar tissue talking.&lt;/p&gt;
&lt;h2 id="the-concurrency-advantage"&gt;The concurrency advantage&lt;/h2&gt;
&lt;p&gt;Agent orchestration is not one request. It is dozens of concurrent flows — tool calls, retrieval hops, validation steps, retries with independent timeout budgets — all competing for resources while a human waits on the other end.&lt;/p&gt;</description></item></channel></rss>