Performance of self hosted next-server degrades when 70.000 new pages are added #63204
Unanswered
Strahbehry
asked this question in
Help
Replies: 2 comments
-
I've set up the default telemetry with Otel. If there's specific requests towards telemetry info I could add this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Experimenting with output: 'standalone', It seems to have made my build 30x slower. I had to limit my ISR paths from 26k pages to 1.8k to test it, but the random slowdowns are gone. Every page is a straight 100 on performance on an unlighthouse test. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
My server slowed down massively after adding more pages. Which caught me offguard since I was very happy with next.js performance and I also couldn't find any earlier post of the sorts implying a large amount of pages (just existing) might be detrimental. I'm seeking help and assistance towards any kind of improvements. Also I'd like to know the technical reason behind the slowdown and CPU usage (and seeming bottleneck) because it does not make logical sense with my current knowledge.
Former situation:
top
on Linux. Sometimes spiking to around 20%Situation with 15.000 pages (slimmed down)
top
on Linux. Sometimes spiking to 120-130%Situation with 70.000 pages
top
on Linux.Current situation, slimmed down to ~27k pages (bare minimum)
top
on Linux.Additional information
If necessary to supply more info I can adjust my build and get specific info.
next.config.mjs:
VPS specifications:
Besides the next-server there's also:
With the fetching server turned off. My next.js deployment has the exact same performance.
Representative
top
snapshot without running unlighthouse against my own site.Representative example while running unlighthouse:
next info
on VPS:Example
No response
Beta Was this translation helpful? Give feedback.
All reactions