Bug Report: Next.js 15.2.4 Build Performance Regression in Docker Build on GIthub actions (7+ mins just to compile) #77624
Comments
github-actions
bot
added
Output
|
Edit: False Alarm. I thought I had mitigated all changes expect 15.2.3 -> 15.2.4 upgrade before I posted. I Had forgot that I was playing with experimental.webpackMemoryOptimizations and had removed the following code from my next.config.js file: webpack: (
config,
{ buildId, dev, isServer, defaultLoaders, nextRuntime, webpack },
) => {
if (config.cache && !dev) {
config.cache.maxMemoryGenerations = 0;
config.cache = Object.freeze({
type: 'memory',
});
}
// Important: return the modified config
return config;
},Turns out this is now mandatory to keep my build under the 500m threshold. |
|
I'm having some compilation issues as well since recently. Before ~15.2 (not sure about the exact version), compilation just took a second or so. Since recently, compilation is slow and takes about 15-30 seconds. I'm talking about just a regular localhost Turborepo & Turbopack setup on a Macbook Pro M1. I now often reboot my dev server to see changes since that's faster than waiting on compilation. -- Update: since I'm using Tailwind CSS v4, perhaps related to tailwindlabs/tailwindcss#17522 |
I am also experiencing this same issue with next.js v15.2.4 development server. It takes more than 15 seconds to compile even the most minute code. |
|
HMR is affected so badly. Rolled back to 15.2.3, otherwise it's absolutely impossible to work. With turbopack, I've been having 15!!!! seconds refresh, without turbopack 7 seconds. Ridiculous downtime. |
Link to the code that reproduces this issue
https://github.com/abhi2425/nextv15.2.4-build-issue
To Reproduce
Current vs. Expected behavior
Current behavior: When building a Next.js 15.2.4 application inside Docker, the build process takes over 10 minutes. Build logs show compilation alone taking ~517 seconds (8.5+ minutes).
I didn't touch my workflow or Dockerfile after upgrading next js version.
Expected behavior: Build should complete in similar time to Next.js 15.1.7 (~2 minutes in Docker) or match the performance seen in non-Docker environments (40-50 seconds locally or in GitHub Actions).
Before Next js 15.1.7
package.json
After upgrading to Next 15.2.4
package.json
Provide environment information
Operating System: Platform: Github Runner, Locally - WSL 2 Arch: x64 Version: Ubuntu 22.04 Binaries: Node: 22.13.0 npm: N/A Yarn: N/A pnpm: 10.4.1 Relevant Packages: next: 15.2.4 (previously 15.1.7) react: 19.0.0 react-dom: 19.0.0 typescript: 5.7.3 Next.js Config: output: "standalone"Which area(s) are affected? (Select all that apply)
Performance, Output
Which stage(s) are affected? (Select all that apply)
Other (Deployed), next build (local)
Additional context
I'm using Docker with the recommended output: "standalone" option in a monorepo setup managed with PNPM. The issue only appears in Docker environments despite using proper cache mounting.
Performance metrics:
Next.js 15.1.7: ~2 minutes in Docker, ~40-50 seconds locally/CI
Next.js 15.2.4: 10+ minutes in Docker (578.2s total), ~40-50 seconds locally/CI
Detailed build logs show the slowdown occurs primarily during compilation:
Compilation alone takes 517 seconds (8.6 minutes) in Docker but finishes in seconds in non-Docker environments.
System details Locally:
Docker in WSL2 (Ubuntu 22.04)
16GB RAM
Multi-stage Docker build with Node 22-alpine images
Same hardware runs local builds 10-12× faster than Docker builds
Troubleshooting attempted:
Verified cache mounts are working properly
Confirmed the exact same code and dependency versions across environments
Tested on different machines with similar results
Reverting to Next.js 15.1.7 immediately resolves the issue
This regression is clearly tied to the Next.js version upgrade from 15.1.7 to 15.2.4. The problem appears to be specific to Docker builds, suggesting a potential issue with how Next.js 15.2.4 utilizes resources in containerized environments.
Docker Build Logs with version 15.2.4
The text was updated successfully, but these errors were encountered: