openclaw - 💡(How to fix) Fix [Bug] v2026.5.22 启动后 Gateway CPU 持续 100%+,导致请求延迟飙升 50-100 倍 [1 pull requests]

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…

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

版本信息

  • 升级前: v2026.5.12 (正常运行)
  • 升级后: v2026.5.22
  • 环境: macOS (Darwin), Node v22.22.0, MacBook Pro

问题描述

升级到 v2026.5.22 后,Gateway 进程持续占用 100%+ CPU(单核满载),导致所有 API 请求延迟飙升 50-100 倍。

实测数据

指标v2026.5.12v2026.5.22恶化倍数
Gateway CPU~5%102%20x
chat.history 延迟~100-200ms11,131ms55-110x
系统负载~2.07.093.5x
Gateway 内存~400MB886MB2.2x

根因分析

v2026.5.22 新增的 "provider auth-state pre-warming" 特性在启动时预热所有模型提供商,导致 Gateway 启动后持续数分钟占满单核 CPU。Release notes 描述此特性可在热路径上将 per-call 成本从 ~20s 降至 ~5ms(4100x 提升),但预热过程本身的 CPU 开销抵消了这一收益。

影响

  • 升级后用户感知到明显卡顿
  • chat.history 等基础 API 从亚秒级变为 10 秒+
  • 必须降级回 v2026.5.12 才能恢复正常

降级后

降级到 v2026.5.12 后,Gateway CPU 立即回落到 ~5%,所有延迟恢复正常。

建议

  1. 考虑将 provider warmup 改为异步后台任务(不阻塞 Gateway ready 信号)
  2. 或加入 warmup 进度/超时控制
  3. 或提供 opt-out 配置选项

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