Remix.run Logo
▲ colek42 30 minutes ago

We should probably be measuring deployable merges to main. The math just doesn't work for pipeline based CI as you add more agents.

Three things matter.

1 -- How many non-conflicting changes can actually be made at one time (Fan Out)

2 -- How long a critical path takes

3 -- How many times you have to run that critical path. Most orgs run it 2-3x, once before the PR in the agent loop, once in CI, and another in the MQ

This is why most orgs cant get past about 12 PRs an hour.

▲dbworku 11 minutes ago | parent [-]

Definitely agree that agent volume will push beyond pipelined CI. Most teams we’ve talked to are still working to get up to 100 PR/hour.