Static routes still using CPU after upgrading to Next.js 16 with cacheComponents: true

[magictalent]

Summary

After migrating my app from Next.js 15 to 16 and enabling cacheComponents: true, I noticed that routes marked as static (dynamic = "force-static") are still showing CPU usage in the Vercel dashboard.

In Next.js 15, these routes were fully static (no CPU usage). But in Next.js 16, even with "use cache" in both page.tsx and layout.tsx, Vercel shows activity as if the routes are still rendered on the server.

I’d like to understand how component caching affects static routes and how to make them behave like SSG or CSR routes again (with zero CPU usage).

Additional information

Next.js version: 16.0.1
Node.js version: 22 (AWS Lambda default)
Deployment: Vercel (Serverless)
Configuration: cacheComponents: true
dynamic = "force-static"
"Use cache" added to both page.tsx and layout.tsx

Example

No response