Nextjs 15 requires 4 cores build time

[jynzo94]

I have a Next.js 15 App Router project, and it includes Payload CMS (though that might not be relevant here).

When I build the app using Nixpacks, the build process uses 4 CPU cores (400% CPU).

Is there a way to reduce the number of cores used during the build?

I asked on Twitter and found that there’s a feature request that might help in the future.

I also bought Dokploy Cloud, and as I understand it, the Dokploy Admin is hosted on your infrastructure. So even though the build still hits 400% CPU usage, but its for a shorter period of time.

In comparison, when I run the same Next.js app with Nginx and PM2, the CPU usage stays under 150-200%.

[jynzo94]

I see the docs about "Go to Production" saying its okay. But if there is way to minimize it will be good. Also I wonder what is the best way to build it with github actions for example without docker registry?

[Siumauricio]

The production guide, requires images hosted in a registry, I have seen some ways to limit the resources of a build such as https://docs.docker.com/build/builders/manage/, maybe it would be a good idea to investigate as I have seen that it is possible to limit the consumption of a build using a custom builder.

[jynzo94]

I think the best you can do is to add build server. I tried this on coolify. I tried with self-hosted docker registry but could not setup and my repos in dockerhub was public(free tier).

I think the ultimate setup of dokploy for production apps and freelancing.

• build server
• self-hosted docker registry with good examples how to use it
• database backup
• dokploy instance backup

And in that case u need 2 of the cheapest servers in hetzner with 2 cores and thats all.

I'm talking from prespective of nextjs 15 + mongodb + few more services. I had a lot of issues running my github action, building my docker image inside and etc...

I would help with the implementation even if I know how...

[Siumauricio]

It's actually something similar.

• In fact, using a CI/CD is generally much cheaper than renting a server to build. GitHub Actions has a free tier. I never even reach the limits, so for that reason, I recommend it. Unless you're a company with many projects and builds, having a dedicated server for builds is more cost-effective (there's a feature request for this Custom build server #711).
• You can also create your own self-hosted registry (we have a template for that).
• You can also create backups and for the dokploy instance.

I use this, and it's the easiest and most cost-effective way, at least for me. I only use one server and use the free GitHub minutes to build images.

I think the only bad thing is that you have to write your Docker images or unless you use something like this action https://github.com/marketplace/actions/build-containers-with-nixpacks-and, but if you get it working you have something that you know will work 99% of the time.

[jynzo94]

I really like dokploy more than any other service - coolify, vercel, render and etc.

The server that I used as "build server" is 4 usd from hetzner. So I dont care if I pay +-4usd. For what I love your paas is that it can have predictable price over vercel/render and ways better UX than coolify.

I think really a lot of people can jump on that service if it delivers fast and easy setup for maintaing nextjs/astro apps like. Currently there is big problem hosting nodejs apps like this. Also I think if you push in this direction you can reach a lot.

Btw I just setup github action that works fine, I hope I'll handle it with self-hosted docker registry and S3. But we need tutorials on this 😄 Thanks for the answers!