5 ms·
Another benchmark by maintainer of Vue and Vite, Evan You: https://github.com/yyx990803/vite-vs-next-turbo-hmr https://github.com/yyx990803/vite-vs-next-turbo-h
by colinchartier 4y ago
Another benchmark by maintainer of Vue and Vite, Evan You: https://github.com/yyx990803/vite-vs-next-turbo-hmr https://github.com/yyx990803/vite-vs-next-turbo-hmr
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
Edit: his thoughts as of this hour: https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussions/8 https://github.com/yyx990803/vite-vs-next-turbo-hmr/discussi...
- deleted 4y ago[deleted]
- rektide 4y agoClose but faster. And in some cases ("leaf") faster. The way you phrase it makes it sound like Vite is still faster & Turbopack is getting there. These tweets seem to indicate Turbopack is faster.
- rk06 4y agoTurbopack is indeed faster, which makes it more confusing. Like why not use the actual verifiable "apple to apple" benchmark results? Even in this article, they do not refer to that acknowledgement, which because it was from a competiting OSS author, would have a lot more weight
- leerob 4y agoEvan is credited in the post (this tweet is from three days ago). > 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's work that helped us identify and correct this.
- cjblomqvist 4y agoYes, but the post doesn't comment on all his notes (actually most are not mentioned). Specifically, his note on swc should really be brought up commented I think (after all, they're the ones who compared themselves with Vite, not the other way around).