A look at ziglang/gotta-go-fast: 250 stars on GitHub, written primarily in Zig. Performance Tracking for Zig
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
This project exists to track various benchmarks related to the Zig project
regarding execution speed, memory usage, throughput, and other resource
utilization statistics.
The goal is to prevent performance regressions, and provide understanding
and exposure to how various code changes affect key measurements.
See the latest results
Strategy
This repository is cloned by a Continuous Integration script that runs on every
master branch commit to ziglang/zig and
executes a series of benchmarks using Linux's performance measurement syscalls
(the same thing that perf does). The machine is a dedicated Hetzner server
with a AMD Ryzen 9 5950X 16-Core Processor, an NVMe hard drive, Linux kernel
5.14.14-arch1-1. See more details below in the CPU Details section.
The measurements are stored in a CSV file which is atomically swapped with
updated records when a new benchmark completes. After a new benchmark row is added
to the dataset, it is pushed to https://ziglang.org/perf/records.csv. The
static HTML + JavaScript at https://ziglang.org/perf/ loads records.csv and
presents it in interactive graph form.
Each benchmark gets a fixed amount of time allocated: 5 seconds per benchmark.
For each measurement, there is a min, max, mean, and median value. The best and
worst runs according to Wall Clock Time are discarded to account for system
noise.
Measurements Collected
Wall Clock Time
Peak Resident Set Size (memory usage)
How many times the benchmark was executed in 5 seconds
These measurements should only be taken for a Zig compiler that has passed the
full test suite, and the $ZIG_EXE command should be a release build matching the
git commit of $COMMIT_SHA1. $COMMIT_TIMESTAMP is required to be in the format
given by --pretty=format:%at.
This will add 1 row per benchmark to records.csv for the specified commit.
The CI script should then push records.csv and manifest.json to the server so
that the frontend HTML+JavaScript can fetch them and display the information.
Backfilling Data
$ZIG_GIT_SRC must be a git clone of zig, with a build-backfill folder
configured with CMake already. It needs to be configured this way:
This ninja install creates stage1/bin/zig which is left untouched, and then
ninja (without the install argument) is used for older zig versions when going
through the commits.
commits.txt is a file containing whitespace-separated git commit hashes.
Use an absolute path for the ending $ZIG_EXE argument which is in a subdirectory
of the zig source tree used to build the zig binary. Some of the benchmarks
want to learn the zig source checkout path in order to test stuff.
Does ziglang/gotta-go-fast have a project website?
No homepage URL was recorded for ziglang/gotta-go-fast in TopGit's last sync. The README tab above frequently contains screenshots and demo links, or check the repository description on GitHub.
Is ziglang/gotta-go-fast open source?
Yes — ziglang/gotta-go-fast ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/ziglang/gotta-go-fast.
What is ziglang/gotta-go-fast?
ziglang/gotta-go-fast (ziglang/gotta-go-fast) is a Zig project on GitHub. From the project's own README: Performance Tracking for Zig
What license does ziglang/gotta-go-fast use?
ziglang/gotta-go-fast is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where do I read more about ziglang/gotta-go-fast?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/ziglang/gotta-go-fast is the definitive source.
Read full README in the tab above.
Is gotta-go-fast worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of gotta-go-fast.