fix(deploy): double reference collector memory watermarks for catalog growth - #574
Conversation
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 71ac5c4466
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
… growth A 2026-08-01 shadow gate (invocation 329edad2) failed on memory.events high growth: the tracked catalog (6509 markets, 316k retained trade ids) outgrew the 672MiB/768MiB pair calibrated for a smaller catalog. Raise both the production and shadow units to 1536MiB/2048MiB and document the new measurement in the README calibration history. Refs #553
b57d389 to
861b7a9
Compare
1 participant
Change contract
Raise the polymarket reference collector memory watermarks 672MiB/768MiB → 1536MiB/2048MiB in both the production and shadow units, with the new measurement documented in the README calibration history.
Evidence
2026-08-01 shadow gate invocation 329edad2 failed on
memory.events highgrowth during cold-start backfill. Catalog has grown to 6509 tracked markets / 316k retained trade ids since the July calibration (586-606MiB peaks). Host drop-in for the shadow template is already applied (interim, controller-authorized); this PR is the durable fix and covers the production unit the cutover will enable.Out of scope
Dependency / merge order
None. Note: the currently staged candidate's control bundle predates this change; the gate is unblocked via the host drop-in until the next release.
Focused validation
test-polymarket-raw-ops-control-plane.shPASS (pins updated)test-polymarket-raw-ops-stage.shPASSRollout / rollback impact
Takes effect on next release install; host interim state matches. Rollback = revert.
Issue relationship
Refs #553