Slow build? Profile and find out why.

Record, visualize, and speed up your project's compilation, no matter the language or build system.

macOS
Windows
Linux
A recording of LLVM's compilation

Profiling a build near you

AppleDelta Air LinesMozillaSecond Half GamesRhino 3DBond Home

Works With Your Build

Profile any build system and any language without changing the build config, thanks to OS-level process capture.

Cargo
Maven
Ninja
MSBuild
Shell Scripts
Make
Visual Studio
Zig
Webpack
Gradle
Rust
esbuild
CMake
TypeScript
Clang
Bazel
Xcode
Swift
Meson
Go
Python

Find the Slow Process

Survey every process in your build on the timeline, with child processes neatly nested inside their parent.

What The Fork's timeline showing every file compiled during an LLVM build, with the selected process's duration and files read below

Surfaces the Things Slowing Your Build

What's slow

  • Bloated Dependencies

    Evaluate if slow dependencies are worth keeping

  • Large Source Files

    Refactor large or template-heavy files

  • Inefficient Tooling

    Identify a slow linker or JavaScript bundler to swap out.

What's wasted

  • Duplicate Work

    Catch files that get compiled more than once.

  • Missed Parallelism

    Spot commands that could've run in parallel.

  • Unnecessary Rebuilds

    See what needlessly recompiles after a one-line change.

What The Fork's timeline showing a Firefox build's Rust crates and C++ files, with a selected time range and the selected rustc process's details below

See Every Detail

See each process's full command, working directory, total runtime, and more.

The details panel of What The Fork, showing the selected rustc process's information

Profile Huge Builds

Enjoy a buttery smooth experience even when viewing more than 100,000 processes.

Debug CI locally

Record a build in CI and view the profile on your local machine.

Watch Live

Find problems early in the build without waiting for the whole build to finish.

Dig a Little Deeper

Explore in-depth timing information for rustc, clang, and swiftc, so you can see which files, templates, and compiler passes take the most time.

SectionTime (s)Percent
Machine code generation1.04531.3%
LLVM passes0.62218.6%
Type checking0.38211.4%
Linking0.2567.7%
Macro expansion0.1945.8%
Borrow checking0.1895.7%
Monomorphization0.1504.5%
Crate metadata generation0.1283.8%
LLVM IR generation0.0842.5%
MIR safety/effect checks0.0481.4%
Lints and other validation0.0401.2%
Parsing0.0290.9%
LLVM optimization0.0230.7%
Name resolution0.0090.3%
Other work0.0040.1%
QueryTime (s)Count
regex_syntax::unicode_tables::case_folding_simple::CASE_FOLDING_SIMPLE0.23548
regex_syntax::unicode_tables::property_bool::BY_NAME0.22748
regex_syntax::hir::print::{{impl}}[3]::visit_pre0.15251
regex_syntax::ast0.12325
regex_syntax::hir0.08325
regex_syntax::unicode_tables::general_category::BY_NAME0.07948
regex_syntax::unicode_tables::script::BY_NAME0.06848
regex_syntax::unicode_tables::script_extension::BY_NAME0.06548
regex_syntax::unicode::ages::imp::AGES0.05748
regex_syntax::unicode_tables::property_values::PROPERTY_VALUES0.04648
regex_syntax::unicode_tables::sentence_break::BY_NAME0.03948
regex_syntax::unicode_tables::case_folding_simple0.03724
regex_syntax::error::{{impl}}[6]::fmt0.03651
regex_syntax::hir::literal::{{impl}}[7]::keep_first_bytes0.03647

Readable at a Glance

Commands and their arguments get summarized in the timeline.

~/.mozbuild/clang/bin/clang++ -c -MD -MP -fPIC -Wall -Wcomma -pthread -Wformat -DDEBUG=1 -fno-rtti -gdwarf-4 -Wno-psabi -Wempty-body -Wtype-limits -stdlib=libc++ -Wsign-compare -Werror=format -DEXPORT_JS_API -fno-math-errno -fno-exceptions -funwind-tables -Wpointer-arith -Wclass-varargs -Wloop-analysis -Wthread-safety -DMOZILLA_CLIENT -fno-aligned-new -DJS_CACHEIR_SPEW -DMOZ_HAS_MOZGLUE -Wempty-init-stmt -Wformat-security -ffp-contract=off -Wunreachable-code -fvisibility=hidden -Wstring-conversion -fcolor-diagnostics -DJS_STRUCTURED_SPEW -Wignored-qualifiers -fno-strict-aliasing -Wno-invalid-offsetof -fstrict-flex-arrays=1 -Wimplicit-fallthrough -Wduplicate-method-arg -Wno-inline-new-delete -Wno-vla-cxx-extension -fno-sized-deallocation -fno-omit-frame-pointer -Wformat-type-confusion -Wfloat-zero-conversion -Wenum-float-conversion -Wobjc-signed-char-bool -Wno-error=array-bounds -fstack-protector-strong -Wno-range-loop-analysis -Wduplicate-method-match -Wunreachable-code-return -mmacosx-version-min=10.15 -DMOZ_SUPPORT_LEAKCHECKING -Wbitfield-enum-conversion -Wunused-but-set-parameter -Wenum-compare-conditional -MF .deps/StoreBuffer.o.pp -fvisibility-inlines-hidden -DWASM_SUPPORTS_HUGE_MEMORY -Wfloat-overflow-conversion -Wno-error=atomic-alignment -Wno-unknown-warning-option -Wno-deprecated-this-capture -Wmissing-method-return-type -Wsuper-class-method-mismatch -Wsemicolon-before-method-body -Wno-error=free-nonheap-object -Wno-error=deprecated-builtins -ftrivial-auto-var-init=pattern -Wno-error=deprecated-declarations -Werror=unguarded-availability-new -Wno-error=builtin-macro-redefined -isysroot ~/.mozbuild/MacOSX15.5.sdk -Wno-deprecated-enum-enum-conversion -I~/Developer/3rdParty/firefox/js/src/gc -Wshadow-field-in-constructor-modified -I~/Developer/3rdParty/firefox/obj-aarch64-apple-darwin24.6.0/js/src/gc -Wtautological-constant-in-range-compare -Wno-deprecated-anon-enum-enum-conversion -Wno-error=tautological-type-limit-compare -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_DEBUG ~/Developer/3rdParty/firefox/js/src/gc/StoreBuffer.cpp -I~/Developer/3rdParty/firefox/obj-aarch64-apple-darwin24.6.0/js/src -I~/Developer/3rdParty/firefox/js/src -I~/Developer/3rdParty/firefox/obj-aarch64-apple-darwin24.6.0/dist/include -include ~/Developer/3rdParty/firefox/obj-aarch64-apple-darwin24.6.0/js/src/js-confdefs.h -o StoreBuffer.o

Turns this

Into this

Compile StoreBuffer.cpp

Developers Forking Love It

“We managed to shave a minute off of an 8 minute build. We will definitely be using this more.”

Callum SykesCallum SykesEngineer, McNeel

“Super interesting, novel, and useful — lets me dive directly into performance issues.”

Will TooheyWill TooheyEngineer, Mon.im

FAQ

Why not use -ftime-trace or cargo --timings?

They're great for looking inside a single tool, but each one only sees its own part of the build and requires modifying the project build system and extra tooling to visualize the results.

How do I integrate with my build system?

After downloading and starting What The Fork, all you have to do is click record and then start your build. No changes to your project or build system are necessary.

Does it slow down builds?

No, we record process start and end events from the OS, which are infrequent and low overhead. With in-depth compiler profiling turned on, compiler processes (like swiftc, rustc, and clang) can run between 1% and 5% slower depending on how efficient their self-profiling feature is. Other processes are not affected.

System requirements?

At least macOS 13.5, Windows 10, or Linux kernel 5.8.

What permissions does it need?
  • macOS uses an Endpoint Security extension. macOS requires those extensions to have Full Disk Access, but we don't actually access any files.
  • The Windows app runs as admin so it can access the process events.
  • Linux needs the cap_bpf and cap_perfmon capabilities.
What data leaves my machine?

What The Fork runs entirely locally, and your data never leaves your machine. We do not collect telemetry. It occasionally checks that the license is valid and if there are updates available.

Ready to Get Started?

Try profiling your build now, it's easy.

Download