Skip to content

perf: cap per-cycle concurrency and back off secondary limits - #61

Merged
Skeyelab merged 1 commit into
mainfrom
perf/bounded-fanout
Sep 29, 2026
Merged

Skeyelab merged 1 commit into
mainfrom
perf/bounded-fanout

Conversation

@Skeyelab

Copy link
Copy Markdown
Member

A cycle launched every Repo fetch at once. GitHub's secondary rate
limit keys on concurrency, so the burst tripped it with the hourly
budget untouched. Fetches are now capped at 4 in flight.

A secondary limit without Retry-After now holds the token for 60s
instead of retrying next cycle, and rate-limited tokens appear in the
title bar alongside paced ones rather than only as stale rows.

Closes #40


Stack created with GitHub Stacks CLI • Give Feedback 💬

@Skeyelab
Skeyelab added this pull request to stack #63 September 29, 2026 03:35
A cycle launched every Repo fetch at once. GitHub's secondary rate
limit keys on concurrency, so the burst tripped it with the hourly
budget untouched. Fetches are now capped at 4 in flight.

A secondary limit without Retry-After now holds the token for 60s
instead of retrying next cycle, and rate-limited tokens appear in the
title bar alongside paced ones rather than only as stale rows.

Closes #40
@Skeyelab
Skeyelab merged commit f668f99 into main Sep 29, 2026
3 checks passed
@Skeyelab
Skeyelab deleted the perf/bounded-fanout branch September 29, 2026 03:50
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.

Poller trips GitHub's secondary rate limiter: unbounded per-tick fan-out, no conditional requests

1 participant