openclaw - 💡(How to fix) Fix Control UI: sessions.list polling too aggressive (8s) [4 comments, 2 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#59317Fetched 2026-04-08 02:26:05
View on GitHub
Comments
4
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×4

The Control UI (web dashboard) polls sessions.list every 8 seconds, which causes noticeable CPU spikes when the gateway is slow or under load.

Root Cause

The Control UI (web dashboard) polls sessions.list every 8 seconds, which causes noticeable CPU spikes when the gateway is slow or under load.

RAW_BUFFERClick to expand / collapse

Description

The Control UI (web dashboard) polls sessions.list every 8 seconds, which causes noticeable CPU spikes when the gateway is slow or under load.

Expected Behavior

Polling interval should be configurable or set to a more reasonable default (30-60 seconds).

Environment

  • OpenClaw version: 2026.3.28
  • OS: macOS (arm64)

Suggested Fix

Increase default polling interval to 30-60 seconds, or make it configurable via settings.

extent analysis

TL;DR

Increase the default polling interval to 30-60 seconds or make it configurable to reduce CPU spikes.

Guidance

  • Review the current implementation of sessions.list polling in the Control UI to understand how the interval is set.
  • Consider adding a configuration option to allow users to adjust the polling interval based on their specific needs.
  • Evaluate the impact of increasing the polling interval on the overall performance and responsiveness of the Control UI.
  • Investigate potential optimizations to the sessions.list endpoint to reduce the load on the gateway.

Example

No specific code example is provided due to lack of implementation details, but the fix might involve modifying a configuration file or adding a settings option to the Control UI.

Notes

The suggested fix assumes that increasing the polling interval or making it configurable will not introduce significant delays or inconsistencies in the Control UI. Further testing is needed to verify the effectiveness of this change.

Recommendation

Apply workaround: Increase the default polling interval to a reasonable value (e.g., 30-60 seconds) as a temporary solution until a configurable option can be implemented, to reduce CPU spikes and improve overall system performance.

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