vitejs/rolldown-vite-perf-wins

Perf wins when users migrate from Vite to Rolldown-powered-Vite, with receipts

68

stars

24

commits

TypeScript

primary language

Sep 5, 2025

updated

README

Rolldown-Vite Performance Wins

A collection of perf improvement stats when users switch from current Vite (powered by Rollup) to Rolldown-powered-Vite.

Interested in trying it yourself? Check out the guide. Got cool results to share? PR welcome!

Results

The resource table below summarizes results of individual applications, comparing build performance across various JavaScript projects using different build tools and configurations, both closed and open source. The Build Speed Change column* indicates how many times faster the build process is with rolldown-vite compared to plain Vite, always measured with all available native plugins enabled unless noted otherwise (see notes 1 and 2 below).

ProjectSourceSocialPlain ViteRolldown-Vite (no native 1)Rolldown-Vite (native v1 2)Build Speed ChangeBuild Memory Usage Change
OutlinePRTwitter47.27s5.40s2.12s22.3x-
StructDB(private repo)Website20.98s4.53s1.19s17x-
ExcalidrawGitHubTwitter22.9s-1.4s16x-
PLAID, inc. (front end 1)-Bluesky1m 20s10s5s16x-
Bright software(private repo)website4m34s1m20s18s15.22x-
Vibe DashboardGitHubPR4.3s-315ms13.6x-
Particl-Twitter 1, Twitter 21m 2s (Vite), 3m (Next.js)27.16s6.36s9.7x
(28.8x compared to Next.js)
-
Meess (Server build)-Twitter2.9s0.82s0.35s8.29x-
PLAID, inc. (front end 2)-Bluesky40s9s5s8x-
Halo (Client build)GitHubTwitter18.98s3.19s2.35s8x-
Meess (Client build)-Twitter3.3s0.85s0.48s6.88x-
GitLabMR 180509Twitter2.5m1m (esbuild for minification)~22s6.82x100x
bzbub2-Reddit Comment 1, Reddit Comment 233.56s10.22s4.97s6.8x-
Saurabh-Twitter5m 10s1m 4s53s5.8x-
Ecksters-Reddit Comment 1, Reddit Comment 248s25s5.5s5.45x-
Payfit-Twitter55s-11.74s4.7x-
Acre Software(private repo)website1m54s38.96s25.41s4.49x-
Todor Andonov-Twitter47s-12s4x-
Sanity-Bluesky21.95.1s-4x (no native plugins)-
AppwritePR 1933Twitter12m 27s5m 38s3m 21s3.7x4x
ast-grepGitHubTwitter23.9s8.71s6.86s3.5x-
hanford-Discord Thread5m-1m 30s (only native resolver)3.33x (only native resolver)-
Mercedes-Benz.io-Blog Post---3x-
Minimal Nuxt.js applicationCodSpeed-5.4s2.1s-2.6x-
Storybook-Bluesky80s56s51s1.56x-

Footnotes

  1. Native plugins were not enabled by default before rolldown-vite v7.1.2 2

  2. A lot of native plugins are enabled by default since rolldown-vite v7.1.2 as "first generation" of native plugins support. 2

Contributors

TheAlexLichter

18 commits

yyx990803

2 commits

0x2f0

1 commits

parkuman

1 commits

vitejs/rolldown-vite-perf-wins

Perf wins when users migrate from Vite to Rolldown-powered-Vite, with receipts

68

stars

24

commits

TypeScript

primary language

Sep 5, 2025

updated

README

Rolldown-Vite Performance Wins

A collection of perf improvement stats when users switch from current Vite (powered by Rollup) to Rolldown-powered-Vite.

Interested in trying it yourself? Check out the guide. Got cool results to share? PR welcome!

Results

The resource table below summarizes results of individual applications, comparing build performance across various JavaScript projects using different build tools and configurations, both closed and open source. The Build Speed Change column* indicates how many times faster the build process is with rolldown-vite compared to plain Vite, always measured with all available native plugins enabled unless noted otherwise (see notes 1 and 2 below).

ProjectSourceSocialPlain ViteRolldown-Vite (no native 1)Rolldown-Vite (native v1 2)Build Speed ChangeBuild Memory Usage Change
OutlinePRTwitter47.27s5.40s2.12s22.3x-
StructDB(private repo)Website20.98s4.53s1.19s17x-
ExcalidrawGitHubTwitter22.9s-1.4s16x-
PLAID, inc. (front end 1)-Bluesky1m 20s10s5s16x-
Bright software(private repo)website4m34s1m20s18s15.22x-
Vibe DashboardGitHubPR4.3s-315ms13.6x-
Particl-Twitter 1, Twitter 21m 2s (Vite), 3m (Next.js)27.16s6.36s9.7x
(28.8x compared to Next.js)
-
Meess (Server build)-Twitter2.9s0.82s0.35s8.29x-
PLAID, inc. (front end 2)-Bluesky40s9s5s8x-
Halo (Client build)GitHubTwitter18.98s3.19s2.35s8x-
Meess (Client build)-Twitter3.3s0.85s0.48s6.88x-
GitLabMR 180509Twitter2.5m1m (esbuild for minification)~22s6.82x100x
bzbub2-Reddit Comment 1, Reddit Comment 233.56s10.22s4.97s6.8x-
Saurabh-Twitter5m 10s1m 4s53s5.8x-
Ecksters-Reddit Comment 1, Reddit Comment 248s25s5.5s5.45x-
Payfit-Twitter55s-11.74s4.7x-
Acre Software(private repo)website1m54s38.96s25.41s4.49x-
Todor Andonov-Twitter47s-12s4x-
Sanity-Bluesky21.95.1s-4x (no native plugins)-
AppwritePR 1933Twitter12m 27s5m 38s3m 21s3.7x4x
ast-grepGitHubTwitter23.9s8.71s6.86s3.5x-
hanford-Discord Thread5m-1m 30s (only native resolver)3.33x (only native resolver)-
Mercedes-Benz.io-Blog Post---3x-
Minimal Nuxt.js applicationCodSpeed-5.4s2.1s-2.6x-
Storybook-Bluesky80s56s51s1.56x-

Footnotes

  1. Native plugins were not enabled by default before rolldown-vite v7.1.2 2

  2. A lot of native plugins are enabled by default since rolldown-vite v7.1.2 as "first generation" of native plugins support. 2

Contributors

TheAlexLichter

18 commits

yyx990803

2 commits

0x2f0

1 commits

parkuman

1 commits

Languages

TypeScript

100.0%