Turbopack Performance Benchmarks

Another benchmark by maintainer of Vue and Vite, Evan You: <a href="https:&#x2F;&#x2F;github.com&#x2F;yyx990803&#x2F;vite-vs-next-turbo-hmr" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yyx990803&#x2F;vite-vs-next-turbo-hmr</a><p>He seems to imply that Turbopack is very close in performance to existing tooling like Vite in his benchmark, and not 10x better in common cases<p>Edit: his thoughts as of this hour: <a href="https:&#x2F;&#x2F;github.com&#x2F;yyx990803&#x2F;vite-vs-next-turbo-hmr&#x2F;discussions&#x2F;8" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yyx990803&#x2F;vite-vs-next-turbo-hmr&#x2F;discussi...</a>

I am very excited for Turbopack.<p>I hope to see this considered by the Angular team. Angular is tightly coupled with webpack, however, they&#x27;ve been experimenting with ESBuild, which is included in Angular 14. Vite has been tested by an Angular team member and reported some promising results. I just hope they don&#x27;t tightly couple the implementation with ESBuild and fall into the same issue again.<p>Back to Turbopack:<p>&gt; Turbopack is up to 10x and 700x faster than existing approaches.<p>The 700x speed gain compared to webpack is for dev mode changing 30000 files at once.. I understand that it scales very well. But is it realistic to boast about unrealistic scenarios? It erks me.

As a dev who avoids build steps entirely in web stacks, hearing that 1.1 sec startup is excellent, or 10-700x faster than the norm seems strange - I&#x27;ve gotten so used to stuff being instant.<p>If you haven&#x27;t tried coding a little closer to the &quot;metal&quot; (vanilla js&#x2F;css&#x2F;html) I definitely recommend it. Browsers give you a lot out of the box now, and life without builds is sweet - fast iteration time, perfect in-browser dev tool support, and vastly reduced codebase complexity.

Here&#x27;s the bulk of the code used to generate the code they&#x27;re building: <a href="https:&#x2F;&#x2F;github.com&#x2F;vercel&#x2F;turbo&#x2F;blob&#x2F;main&#x2F;crates&#x2F;turbopack-create-test-app&#x2F;src&#x2F;test_app_builder.rs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vercel&#x2F;turbo&#x2F;blob&#x2F;main&#x2F;crates&#x2F;turbopack-c...</a><p>They&#x27;re building basically the same thing over and over again. This surprised me, given their intro post: <a href="https:&#x2F;&#x2F;vercel.com&#x2F;blog&#x2F;turbopack" rel="nofollow">https:&#x2F;&#x2F;vercel.com&#x2F;blog&#x2F;turbopack</a><p>Relevant quote:<p>&gt; Turbopack is built on Turbo: an open-source, incremental memoization framework for Rust. Turbo can cache the result of any function in the program. When the program is run again, functions won&#x27;t re-run unless their inputs have changed. This granular architecture enables your program to skip large amounts of work, at the level of the function.<p>I&#x27;d be curious to see if a real-world app (or even one generated with more variety in components) showed comparable performance numbers

Something that isn&#x27;t clear to me: Why, exactly, is it so much faster than even its own build tool(swc)?<p>In other words, what&#x27;s speeding up here isn&#x27;t build speed, but the ability to download the updated changes. Right? Or am I wrong?

&gt; Turbopack and Next.js 13.0.1 are out addressing a regression that snuck in prior to public release and after the initial benchmarks were taken. We also fixed an incorrect rounding bug on our website (0.01s → 15ms). We appreciate Evan You&#x27;s work that helped us identify and correct this.<p>Does this mean they don&#x27;t have a CI to run benchmarks to gate regressions?

Weird that rebuild is absent in these benchmarks.

Has this even been released? I went to look for a release on the repo and website and only saw instructions for using it with Next js. Might as well call it Next.js if it can&#x27;t easily be used with anything else. The only way I found to build it was from the master branch. The latest tip in master is not a release.

it doesn&#x27;t make much sense to compare a tool that only works with nextjs with webpack and vite

Good on them make a correction

will this work with existing webpack configs? and with babel? i need babel..