openclaw - 💡(How to fix) Fix Slow startup with multiple providers (models.list takes 30+ seconds) [1 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#62364Fetched 2026-04-08 03:05:26
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
2
Author
Participants

Code Example

15:11:44+08:00 [gateway] ready (3 plugins, 2.4s)  ? Gateway itself starts fast
...
15:13:01+08:00 [ws] ? res ? chat.history 33773ms
15:13:01+08:00 [ws] ? res ? models.list 33676ms  ? This blocks startup
RAW_BUFFERClick to expand / collapse

Describe the bug: After upgrading from 2026.3.28 to 2026.4.5, Gateway startup time increased significantly due to provider validation during models.list.

Version comparison:

2026.3.282026.4.5
Startup time~12s~85s
models.listNot logged33.7s
Providers configured99

Logs (2026.4.5):

15:11:44+08:00 [gateway] ready (3 plugins, 2.4s)  ? Gateway itself starts fast
...
15:13:01+08:00 [ws] ? res ? chat.history 33773ms
15:13:01+08:00 [ws] ? res ? models.list 33676ms  ? This blocks startup

Configuration:

  • 9 providers (bailian, deepseek, scnet, infinigence, etc.)
  • 50+ models
  • Config file: 114KB

Expected behavior: Startup should remain fast regardless of provider count. Provider validation could be:

  1. Lazy-loaded - validate on first use, not at startup
  2. Parallel - check providers concurrently
  3. Optional - a config flag to disable startup validation

Environment:

  • Windows 10
  • Node v24.14.0
  • OpenClaw 2026.4.5

extent analysis

TL;DR

The most likely fix is to implement lazy-loaded provider validation to prevent blocking startup.

Guidance

  • Review the models.list function to identify the cause of the significant increase in execution time and consider optimizing or refactoring it.
  • Investigate the possibility of implementing parallel provider validation to reduce the overall startup time.
  • Consider adding a configuration flag to allow for optional startup validation, enabling users to choose between fast startup and thorough validation.
  • Analyze the logs to determine if there are any specific providers that are causing the slowdown and prioritize optimization efforts accordingly.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details of the models.list function or the provider validation mechanism.

Notes

The increased startup time may be due to the addition of new providers or changes in the validation logic between versions 2026.3.28 and 2026.4.5. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by implementing lazy-loaded provider validation, as this approach is likely to significantly reduce the startup time without requiring major changes to the existing codebase.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING