next-server process is loaded 100% #82226
-
SummaryIn the production version, with a huge load on the site (SEO Spider frog in 4 windows at maximum speed), one node-server process loads 100% and the site starts to work very poorly Additional informationNo response ExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi @Ohthatorh, Thanks for raising this. Seeing a next-server Node.js process at 100% CPU under heavy load like multiple SEO spiders running is not uncommon, but it does indicate some performance bottlenecks or resource limits being hit. Here are some suggestions to improve performance and reduce CPU usage:
Use ISR (Incremental Static Regeneration) or Static Site Generation (SSG) wherever possible to reduce server rendering on each request.
Configure your server or CDN to throttle or block aggressive crawlers that hammer your site. This helps prevent overload.
Offload static assets and cacheable pages via a CDN to reduce load on your server.
Look for any heavy synchronous code or slow database queries that block the event loop.
If you expect heavy traffic, deploy multiple Node.js instances behind a load balancer.
Use profiling tools to identify hot paths or memory leaks causing CPU spikes. If you provide more details about your setup, caching strategy, and hosting environment, I can offer more specific advice. |
Beta Was this translation helpful? Give feedback.
-
Hello! Thank you! Deploying additional Node.js instances did help, since everything else was already configured (CDN, caching and SSR). |
Beta Was this translation helpful? Give feedback.
Hi @Ohthatorh,
Thanks for raising this. Seeing a next-server Node.js process at 100% CPU under heavy load like multiple SEO spiders running is not uncommon, but it does indicate some performance bottlenecks or resource limits being hit.
Here are some suggestions to improve performance and reduce CPU usage:
Use ISR (Incremental Static Regeneration) or Static Site Generation (SSG) wherever possible to reduce server rendering on each request.
Configure your server or CDN to throttle or block aggressive crawlers that hammer your site. This helps prevent overload.
Offload static assets and cacheable pages via a CDN to reduce load on your …