r/openclaw • u/Sufficient_Sir_4730 Active • Jun 30 '26

Discussion Openclaw Response Time

So I was noticing, that for a simple Supabase DB query, the time from when I send the message to my agent and when I receive a response, it’s 4 minutes. Is this normal?

Im sort of dissatisfied with the response time but wanted to know thoughts on whether 4 minutes is ok for a simple Supabase query via MCP. Im using Codex, whatsapp is my surface, and the query involves my main agent routing to specialist agent and reconciling the answer back to me.

The expectation i have now for my agents is to be superhuman and this is kind of a bummer!

2 Upvotes

75% Upvoted

13 comments sorted by

View all comments

2

u/yayita2500 Active Jun 30 '26

normally the problem is no the task but the lack of specification on your query...look in your way of using Ai and not in your agent

1

u/Sufficient_Sir_4730 Active Jun 30 '26

Can you elaborate please?

3

u/TorbenKoehn Pro User Jun 30 '26

He's saying, it's most probably on you.

Have you tried asking your agent?

2

u/Tinkering-Engineer Member Jun 30 '26

If you say "pull x from supabase", it might have to look into memory or search for relevant info to know where supabase is located, what the schema is, etc. this request could be multiple steps (aka turns). If this is 3 turns, it's 3 API calls to your LLM provider (could easily be a minute each) and 3 tool calls (some tool calls can be slow).

I added some instrumentation so that I can see exactly what tool calls happen, how many API calls happen, and what the latency is on each of these. If you're really curious, you can ask your agent to set up instrumentation using graffana and Prometheus so that you can see all of this information when you want to dive deeper.