Skip to content

DO NOT MERGE: load-test bit_pr on xlarge with a full dependents cascade - #10601

Closed
luvkapur wants to merge 2 commits into
masterfrom
ci-pr-loadtest-xlarge
Closed

DO NOT MERGE: load-test bit_pr on xlarge with a full dependents cascade#10601
luvkapur wants to merge 2 commits into
masterfrom
ci-pr-loadtest-xlarge

Conversation

@luvkapur

Copy link
Copy Markdown
Member

Throwaway experiment for #10597: a comment-only change to teambit.component/component (~308 direct importers) forces the auto-snap dependents cascade, validating the 2xlarge→xlarge downgrade against the memory-heavy worst case instead of a 2-component lane. Will be closed and the branch deleted once the bit_pr job result (duration / credits / OOM-or-not) is recorded.

🤖 Generated with Claude Code

luvkapur and others added 2 commits August 11, 2026 14:48
…r sizing)

Insights (30d, all branches): ~4.8M credits/month (~$2.9k) —
e2e_test 3.41M (71%), bit_pr 800k (17%), e2e_test_bbit 200k, bit_merge 153k.

- stop persisting .pnpm-store: nothing downstream reads it; it inflated the
  workspace every node of every job attaches (~2.7min x 40 e2e nodes/run)
- e2e_test off master pushes: gates nothing there (bit_merge and the merge
  queue don't depend on it); a daily canary now runs in nightly instead
  (~440k credits/month -> ~185k)
- e2e_test parallelism 40 -> 30: per-node fixed setup is the only cost that
  scales with node count (suite time is constant); ~4min wall-clock cost
- bit_pr 2xlarge -> xlarge: build is CPU-bound on a single env, 16 cores were
  idle at 80 credits/min; heap capped at 12GB to fit 16GB RAM (~400k/month
  if it holds — revert to 2xlarge on 'Killed')
- e2e_test_bbit halts on quiet days: no new @teambit/bit version in 24h means
  the previous nightly already bundled+tested the same thing (32 nodes x 30min)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… ci pr on xlarge

Throwaway branch. Forces the auto-snap dependents cascade (~300+ direct
importers) so the 2xlarge->xlarge downgrade in #10597 is validated against
the memory-heavy worst case, not a 2-component lane.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@luvkapur

Copy link
Copy Markdown
Member Author

Experiment concluded via attempt 2 (#10602): the full-cascade lane (98 components) built successfully on xlarge/12GB heap in 25 min with no OOM. This attempt's failure was a transient bit.cloud scope-fetch 500 surfaced as an unhandled rejection — both addressed in #10603. Remote lanes teambit.bit/ci-pr-loadtest-xlarge{,-2} can be janitored.

@luvkapur luvkapur closed this Aug 11, 2026
@luvkapur
luvkapur deleted the ci-pr-loadtest-xlarge branch August 11, 2026 22:56
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.

1 participant