Skip to content

perf: reduce live worker capacity probes#42

Merged
steipete merged 1 commit intoopenclaw:mainfrom
stainlu:stainlu/perf-active-workflow-runs
May 5, 2026
Merged

perf: reduce live worker capacity probes#42
steipete merged 1 commit intoopenclaw:mainfrom
stainlu:stainlu/perf-active-workflow-runs

Conversation

@stainlu
Copy link
Copy Markdown
Contributor

@stainlu stainlu commented May 5, 2026

Reduces repair live-capacity GitHub Actions API probes by fetching recent workflow runs once and filtering active statuses locally. Also avoids an immediate duplicate capacity probe in the wait-for-capacity dispatch loop.\n\nValidation: build:repair, focused live-worker-capacity test, targeted oxlint, targeted oxfmt, git diff --check. Direct build in this checkout is blocked by non-writable generated dist files, so validation ran in /private/tmp/clawsweeper-perf-build.

@steipete
Copy link
Copy Markdown
Contributor

steipete commented May 5, 2026

This optimization is still directionally useful for rate-limit pressure, but the branch is dirty against current main. Please rebase before review/landing.

During the refresh, make sure it composes with the current workflow-active-run fixes on main: live worker/run counting should use supported GitHub data and local filtering, not unsupported gh run list --workflow / status-flag fallbacks. After rebase, please rerun pnpm run check.

@stainlu stainlu force-pushed the stainlu/perf-active-workflow-runs branch from ce2bdb4 to 43fc8f7 Compare May 5, 2026 08:04
@stainlu
Copy link
Copy Markdown
Contributor Author

stainlu commented May 5, 2026

Rebased on current main and reran pnpm run check under Node 24. This now uses the workflow-runs API with local active-status/prefix filtering and avoids the duplicate dispatch capacity probe.

@steipete steipete merged commit 2477968 into openclaw:main May 5, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants