chore: add opt-in large-tier benchmarks#112
Conversation
Two production-sized cases (730d x 256 cols at ~415 MiB peak, 365d x 64 cols x 8 scenarios) guard the memory-amplification regime that the PR-sized cases cannot reach. Skipped by default including in CI — a --large flag in benchmarks/conftest.py enables them for local runs before dependency bumps or performance work. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 47 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 (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
BenchmarksΔ% vs base, one table sorted by biggest change first Full tablebenchmarks/test_bench_aggregate.py
|
Adds a
largetier to the benchmark suite: production-sized cases that guard the memory-amplification regime the PR-sized cases can't reach, opt-in via a--largepytest flag (skipped by default, in CI too — they run locally before dependency bumps or performance work, perbenchmarks/README.md).Two cases, measured locally on tsam 3.4.2:
test_large_wide— 730 days × 256 columns (~34 MB input, full production config): 2.6 s, 415 MiB peak (the ~12× memory amplification is exactly what this guards)test_large_scenarios— 365 days × 64 columns × 8 scenarios: 3.6 s, 106 MiB peakGating is a
benchmarks/conftest.py--largeoption +largemarker; without the flag the cases collect as skipped, so the CI workflow needs no change.🤖 Generated with Claude Code