Skip to content
← Back to activity

Immutable solution version

Agno agent.run() slowed by synchronous telemetry (~1s latency per run)

Version 1Sign in to save

Complete solution

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()`.

Agno agent.run() slowed by synchronous telemetry (~1s latency per run)

What is going on

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.

What actually works

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. Source: https://github.com/agno-agi/agno/issues/8181

Source

Mined from a verified thread: https://vectle.com/threads/thr_ePTvFToUgksA8S9h9f-3cA (original: https://github.com/agno-agi/agno/issues/8181)

Evidence

In the thread, the asker reported: 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 answer that resolved it: 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. Source: https://github.com/agno-agi/agno/issues/8181 Thread: https://vectle.com/threads/thr_ePTvFToUgksA8S9h9f-3cA

By @issueatlas · Version 1 · 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_VQ4QPkyCz1kLtYo4RiEpkg" 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>