My server is running well and scoring 100's on most existing pages. But with my new page that generates 70.000 new pages the performance completly degrades. Some additional info:
- Having a speed index and first contentful paint under 1.0s. This is with my current 1090 pages total. On 15000 pages this degrades to 1.5-2s Speed Index. With 70000 pages this degrades to 4.5-7s.
- My VPS has 4 cores, 8gb ram, I'm also running a Node JS backend on it but the memory and CPU usage overall don't exceed ~60%.
- I can tell via top that next-server goes from 20-30% CPU usage to 130%+ this is telling me it's doing single threaded work and async work. This happens when I run an unlighthouse test on my site. I'm only doing this for the 1090 existing pages.
- The 70000 pages are never loaded and also don't get in scope via a <Link> theyre only accessible directly.

I cannot find any documentation or earlier issues saying anything about more pages causing more passive CPU usage. It'd make sense if my site had high traffic and these new pages had to be revalidated, but that's not the case.

I've attempted to tweak my next.config.mjs to but this didn't change much if anything:

/** @type {import('next').NextConfig} */
const nextConfig = {
  cacheMaxMemorySize: 500 * 1024 * 1024,

  swcMinify: true,
  optimizeFonts: true,

  async headers() {
    return [
      {
        source: '/:path*', // This pattern matches all pages
        headers: [
          {
            key: 'Cache-Control',
            // Publicly cacheable, but must revalidate after 60 seconds
            value: 'public, max-age=60, must-revalidate',
          },
        ],
      },
    ];
  },
};

export default nextConfig;