# Elastic build machines now use Turborepo cache hits to prevent downgrades

DevFeed: [Elastic build machines now use Turborepo cache hits to prevent downgrades](<https://devfeed.tech/articles/elastic-build-machines-now-use-turborepo-cache-hits-to-prevent-downgrades-911.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/elastic-build-machines-now-use-turborepo-cache-hits-to-prevent-downgrades>)

Author: Anthony Shew

Published: 2026-08-24T16:11:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [cpu](<https://devfeed.tech/topics/cpu.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [memory](<https://devfeed.tech/tags/memory.md>)

## AI overview

Vercel's Elastic build machines now account for Turborepo cache hits when deciding whether to downgrade build resources. Warm-cache builds no longer cause a downgrade, helping ensure later cold-cache builds have enough CPU and memory to complete successfully.

## Source excerpt

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. Read more