120x more data, 1.1–1.6x more branch time.
Same branching workflows, data scaled from 250K rows to SF100 (about 120x): MatrixOne grows 1.1–1.6x, DoltDB 68–120x. software_dev (physical ADD COLUMN) did not complete at any tier this round — see the note.
- data_cleaning · 10 workers · MatrixOne
- 37.5 s
- Same point · DoltDB
- 511.6 s
SF100 · order_line 30M rows · 10 / 100 workers
Only the four points where both systems completed are compared. software_dev performs a physical ALTER TABLE ADD COLUMN per step; MatrixOne did not complete it at 10 / 100 / 500 workers, while DoltDB completed 10 / 100. At 250K rows DoltDB was 7.2–33.4x faster, so the two curves cross in between. Speedups vary with scale and do not form a cross-scale ranking.
Full values & methodology
Workflows completed by both · completion time
| Subject | MatrixOne (s) | DoltDB (s) |
|---|---|---|
| data_cleaning · 10 workers | 37.5 | 511.6 |
| data_cleaning · 100 workers | 560.4 | 2,275.7 |
| mcts · 10 workers | 179.0 | 887.5 |
| mcts · 100 workers | 3,169.9 | 5,016.1 |
Conditions & definitions
Git4Data parallel branching at SF100 (order_line 30,000,000 rows, warehouse 100), 10 / 100 / 500 workers; MatrixOne 77dbf546, DoltDB dolt-sql-server:2.2.3; 2026-10-03 delivery. Comparison point at 250,000 rows. Single run per configuration.
Git4Data · SF100 · completed by both
| Workload | Writers | MatrixOne (s) | DoltDB (s) | Speedup | Status |
|---|---|---|---|---|---|
| data_cleaning | 10 | 37.5 | 511.6 | 13.7× | completed |
| data_cleaning | 100 | 560.4 | 2,275.7 | 4.1× | completed |
| mcts | 10 | 179.0 | 887.5 | 5.0× | completed |
| mcts | 100 | 3,169.9 | 5,016.1 | 1.6× | completed |
| software_dev | 10 | n/a | 235.3 | — | not completed |
| software_dev | 100 | n/a | 2,154.1 | — | not completed |
SourcesP0-2 Git4Data · 2026-10-03