Speed
Measured on every release.
Tested on 100,000 commits, 5,000 branches and tags and 10,000 files.
Time
What you wait for.
| Action | At most |
|---|---|
| Start Crabway (window ready to use) | 1 s |
| Open the repository (first rows of the graph) | 300 ms |
| Scroll the graph or a file list | 16 ms per frame |
| Select a commit (details shown) | 100 ms |
| Compare two commits, even the newest with the oldest | 100 ms |
| Open the diff of a 5,000-line file | 200 ms |
| Blame a 5,000-line file | 500 ms |
| Show the history of a file changed in 168 commits (first rows) | 300 ms |
| Search the commits (first match among the newest 10,000) | 400 ms |
| Stage, unstage or discard (lists updated) | 200 ms |
| Change a file on disk (status updated) | 300 ms |
| Open a file with 50 conflicts in the merge tool | 300 ms |
| Tick a line in the merge tool | 16 ms |
| Drop a branch on another (menu shown) | 100 ms |
| Switch to another tab or worktree (as you left it) | 300 ms |
Each time is the best of several runs of the release build. While you scroll, at most 3 frames in 100 may take longer than 16 ms.
Memory and processor
What it holds.
| State | At most |
|---|---|
| Window open, no repository | 250 MB |
| Whole history of 100,000 commits loaded | 300 MB |
| Diff of a 5,000-line file open | 300 MB |
| Twenty repositories open, compared with one | +70 MB |
| Idle, in any state above | 0.5% of one CPU core |
Memory counts everything Crabway holds, at rest. Measured on the CI test machine: [to be filled].
Git, the crab way.
Open your biggest repository.
Crabway is a desktop app. Send yourself the link.