# How to reproduce the 50-agent landing benchmark on your own machine with git-ai

Repo: [feder-cr/git-ai](https://github.com/feder-cr/git-ai) | Difficulty: Intermediate | Time: 45 minutes | Basis: Seen in the wild

Run the repo's acceptance script to compare classic retry-based landing with batched compare-and-swap landing.

**Who it is for:** Engineer evaluating gitai who does not want to trust published numbers without running them

**The problem:** The README claims 200 landed changes versus about 100 for classic landing, but you need to see it on your hardware.

**The outcome:** You get your own landed-count, attempts-per-change and latency figures for 50 agents landing 250 changes with planned conflicts.

## Steps

1. Build the repo with: make build
2. Run the benchmark script at examples/graft/demo/acceptance-phase4.sh
3. Compare the classic and gitai columns for changes landed and attempts per landed change
4. Read doc/graft/BENCH.md for the other agent counts

## Prompt to paste into your agent

```text
In feder-cr/git-ai, run examples/graft/demo/acceptance-phase4.sh after make build and report changes landed, attempts per landed change and p99 latency for classic versus gitai. Verify that the roughly 50 unlanded changes in the gitai run are the planned conflicts.
```

## Caveat

The README numbers come from one 16-core machine and a run without a conflict resolver; a smaller machine will show different lands per minute.

## Seen in the wild

- X (Oct 2026): https://x.com/i/web/status/2111611970294255692

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/feder-cr-git-ai/reproduce-the-50-agent-benchmark/