Menu

Post image 1
Post image 2
Post image 3
Post image 4
Post image 5
1 / 5
0

How Remote Caching decreased publish times by 80%

Vercel News·JJ Kasper·3 days ago
#VAvVBrdZ
#vercel#next#cache#publish#binaries#turborepo
Reading 0:00
15s threshold

Next.js lets developers iterate on their projects faster—but we want to iterate on Next.js itself faster, too . This year, Next.js surpassed 4 million npm downloads for the first time. With over 2,400+ contributors, the core team here at Vercel must craft a developer experience to keep up with such a vast community to develop, test, build, and publish Next.js. Next.js had another first this year: introducing Rust to its core. While adding Rust brings greatly improved performance for developers using Next.js, the tradeoff was an increase in CI time to publish new releases due to the prolonged process of building Rust binaries. Until implementing Turborepo Remote Caching dropped publish times by 80%. Next.js publishing times falling by 80% using Turborepo Remote Cache on Vercel. Link to heading Caching SWC binaries in CI wasn’t enough Turborepo Remote Caching wasn’t the first attempt we made at trying to reduce our time to publish.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More