This benchmark measures how Turbo PRO v2 handles projects of very different sizes — from a tiny toolchain repo to a huge framework mono-repo.

Earlier builds of Turbo struggled with massive workspaces. v2 was rebuilt with performance-first principles, so we ran it against three representative open-source projects.

• Vite — small repo (~73 MB)

• Storybook — medium repo (~1.1 GB)

• React.js — large repo (~1.9 GB)

🖥️ Tested on a MacBook Pro M1 (2021, 16GB RAM).

Below you can see the Turbo tree fully initialized for each project along with the measured first-load time.

Once the initial tree is in place, every file change is reflected in under 100 ms thanks to the Turbo VDOM diff-patch engine — even in the 1.9 GB React repo.

Want to understand what makes all of this possible under the hood? Dive into the technical breakdown of Turbo PRO v2 and discover the new engine, concurrency strategies, and how the Turbo VDOM works.

Turbo PRO v2 proves it can scale from tiny tools to gigantic frameworks while staying fast and stable.

Huge thanks to the community for pushing us toward these performance wins — and stay tuned, we’re just getting started.