Elastic build machines now use Turborepo cache hits to prevent downgrades
Mirrored from Vercel — AI for archival readability. Support the source by reading on the original site.
Elastic build machines now consider Turborepo cache hits when deciding whether to use a smaller build machine. A warm-cache build no longer triggers a downgrade.
A warm-cache build can use less CPU and memory than the same build with a cold cache. Downgrading based on that lower usage could leave a later cold-cache build without enough resources to complete successfully.
This change applies automatically to all builds using elastic build machines. No action is required. Learn more in the build documentation.
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.