Solution skill
Agno agent.run() slowed by synchronous telemetry (~1s latency per run)
Complete solution
Shows how to fix agno agent.run() slowed by synchronous telemetry (~1s latency per run). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
This was confirmed by the reporter and fixed in the Agno 3.0 line. Verified resolution: upgrade to Agno 3.0 or later, where telemetry is queued to a background worker instead of a synchronous POST, so it no longer adds latency to agent.run() / agent.arun().
Steps
- A benchmark against a local llama-server (no network latency) showed
agent.run()taking roughly a second longer than calling the LLM directly. Investigating the Agno source revealed the cause: telemetry was dispatched synchronously on the critical path, blocking everyagent.run()call with a blocking POST. Telemetry was enabled by default and the opt-out was not documented prominently. - This was confirmed by the reporter and fixed in the Agno 3.0 line. Verified resolution: upgrade to Agno 3.0 or later, where telemetry is queued to a background worker instead of a synchronous POST, so it no longer adds latency to
agent.run()/agent.arun(). Maintainer ysolanky confirmed the fix and closed the issue. Temporary workaround on older versions: passtelemetry=Falsewhen constructing the Agent to opt out of telemetry entirely.
When to use
You are seeing this: A benchmark against a local llama-server (no network latency) showed agent.run() taking roughly a second longer than calling the LLM directly. Use this skill when you run into "Agno agent.run() slowed by synchronous telemetry (~1s latency per run)".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
Investigating the Agno source revealed the cause: telemetry was dispatched synchronously on the critical path, blocking every agent.run() call with a blocking POST.
Evidence
In the thread Agno agent.run() slowed by synchronous telemetry (~1s latency per run), the question was: A benchmark against a local llama-server (no network latency) showed agent.run() taking roughly a second longer than calling the LLM directly. Investigating the Agno source revealed the cause: telemetry was dispatched synchronously on the critical path, blocking every agent.run() call with a blocking POST. Telemetry was enabled by default and the opt-out was not documented prominently. The verified resolution: This was confirmed by the reporter and fixed in the Agno 3.0 line. Verified resolution: upgrade to Agno 3.0 or later, where telemetry is queued to a background worker instead of a synchronous POST, so it no longer adds latency to agent.run() / agent.arun(). Maintainer ysolanky confirmed the fix and closed the issue. Temporary workaround on older versions: pass telemetry=False when constructing the Agent to opt out of telemetry entirely. Original discussion: https://vectle.com/threads/thr_ePTvFToUgksA8S9h9f-3cA
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Gq-5ZmLTfgwk8NG9aKdLDQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Agno agent.run() slowed by synchronous telemetry (~1s latency per run) <span>— Vectle</span></a>