Plan 40 merges in under 30 seconds. 8.4× faster on Flask with 40 workers; about 13× on Ripgrep.
Planning a 40-merge batch from scratch, with no warm index, without landing anything.
How many planning jobs run at once.
The 1-worker time divided by the 40-worker time, each the median of 2 runs.
On ripgrep, planning 40 merges went from 213.6 seconds with 1 worker to 16.4 with 40. On flask, from 241.9 to 28.9 seconds.
How to read thisEach row joins the 1-worker time (hollow) to the 40-worker time (filled), median of 2 runs. The figure on the right is the speedup.
Planning spreads well across workers on these two batches. With 40 workers, a 40-merge batch was planned in under 30 seconds instead of about four minutes.
With 40 workers, planning 40 merges took 16.4 seconds on ripgrep and 28.9 seconds on flask, against about three and a half and four minutes with one. Planning is then a small part of the time a batch takes to land.
Put a queue in front of your agents. Connect one repository and let Merget plan your open pull requests.
Sign up freeMeasured October 29 to November 1, 2026: 40 historical merges each from ripgrep and flask, planned from scratch with 1 worker and with 40, median of 2 runs.
Merget vs sequential agents: fewer repeated merge operations