openclaw - 💡(How to fix) Fix [Performance] Gateway takes 50+ seconds per request - plugin tools loading on every request [4 comments, 5 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#75642Fetched 2026-05-02 05:32:25
View on GitHub
Comments
4
Participants
5
Timeline
10
Reactions
5
Timeline (top)
commented ×4cross-referenced ×4closed ×1labeled ×1

Gateway takes 50+ seconds per request for simple messages. The typing indicator appears late, and the actual response is very slow.

Root Cause

This appears to be because plugin specs (41 specs) are being reloaded on every request instead of being cached. Disabling unused plugins (brave, duckduckgo, tavily, web-readability) did not help - the same stages still take the same amount of time.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Gateway takes 50+ seconds per request for simple messages. The typing indicator appears late, and the actual response is very slow.

Steps to reproduce

  1. Send any message to the Gateway via Feishu
  2. Observe the delay before typing indicator appears

Expected behavior

Response time should be under 5 seconds for simple queries.

Actual behavior

Each request takes ~50 seconds total, with these stages:

  • auth: 6.7 seconds
  • core-plugin-tools: 11 seconds
  • system-prompt: 10 seconds
  • stream-setup: 9.4 seconds
  • model-resolution: 3.7 seconds Total startup: 15-16 seconds, prep: 35 seconds.

OpenClaw version

4.29

Operating system

ubuntu 22.04

Install method

npm

Model

minimax

Provider / routing chain

openclaw->kimi-code->minimax

Additional provider/model setup details

This appears to be because plugin specs (41 specs) are being reloaded on every request instead of being cached. Disabling unused plugins (brave, duckduckgo, tavily, web-readability) did not help - the same stages still take the same amount of time.

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Implement caching for plugin specs to reduce the reload time on every request.

Guidance

  • Investigate the plugin spec loading mechanism to identify why caching is not working as expected, focusing on the 41 specs being reloaded.
  • Verify the disabled plugins (brave, duckduckgo, tavily, web-readability) are indeed not contributing to the delay by checking their individual load times.
  • Review the OpenClaw version 4.29 documentation to see if there are any known issues or configuration options related to plugin spec caching.
  • Consider implementing a temporary workaround by reducing the number of plugin specs or optimizing their loading process to improve response times.

Example

No specific code example can be provided without more details on the plugin spec loading mechanism, but a general approach might involve modifying the plugin loading function to check for cached specs before reloading them.

Notes

The provided information suggests that caching plugin specs could significantly reduce the delay, but the root cause of why caching is not currently working needs further investigation. The OpenClaw version and the specific plugins in use might have version-specific quirks or configuration requirements.

Recommendation

Apply workaround: Implement caching for plugin specs or optimize their loading process, as upgrading to a potentially fixed version is not explicitly implied in the given information. This is because the issue seems to be related to the configuration or usage of the current version rather than a known version-specific bug.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Response time should be under 5 seconds for simple queries.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Performance] Gateway takes 50+ seconds per request - plugin tools loading on every request [4 comments, 5 participants]