Server requests and latency increased after upgrading from Next.js 15 to 16
### Link to the code that reproduces this issue https://github.com/carlos-dubon/next-16 ### To Reproduce Upgrade to Next.js version 16 ### Current vs. Expected behavior After upgrading from Next.js 15 to Next.js 16, I noticed that the number of requests effectively doubled. This has resulted in increased server strain and higher response latency. It also seems to require more resources and therefore higher server costs $$$ (good for cloud services I guess?) compared to v15. Server request patterns and performance should remain consistent (or improve) after upgrading. ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000 Available memory (MB): 65536 Available CPU cores: 10 Binaries: Node: 24.10.0 npm: 11.6.1 Yarn: 1.22.22 pnpm: N/A Relevant Packages: next: 15.5.5 // An outdated version detected (latest is 16.0.0), upgrade is highly recommended! eslint-config-next: N/A react: 19.1.1 react-dom: 19.1.1 typescript: 5.9.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Performance ### Which stage(s) are affected? (Select all that apply) Other (Deployed) ### Additional context The screenshot shows the ops/s after deploying v16 around 3:30 PM, I then proceeded to revert back my changes: <img width="1920" height="526" alt="Image" src="https://github.com/u
Posted by carlos-dubon on Oct 28, 2025, 5:45 PM
Tags
Related issues
- [UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
- Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
- Can't download videos from YouTube on cobalt.tools
- `google_service_networking_connection` produce an error when trying to destroy the resource
- WebGPU-based renderer for the editor
- Zed downloads NodeJS binary and npm packages from Internet without user’s consent
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (Network)
[UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
Server requests and latency increased after upgrading from Next.js 15 to 16
Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
Can't download videos from YouTube on cobalt.tools
`google_service_networking_connection` produce an error when trying to destroy the resource
WebGPU-based renderer for the editor
Zed downloads NodeJS binary and npm packages from Internet without user’s consent
FR: Allow custom domains for Tailscale Funnel
Server requests and latency increased after upgrading from Next.js 15 to 16
### Link to the code that reproduces this issue https://github.com/carlos-dubon/next-16 ### To Reproduce Upgrade to Next.js version 16 ### Current vs. Expected behavior After upgrading from Next.js 15 to Next.js 16, I noticed that the number of requests effectively doubled. This has resulted in increased server strain and higher response latency. It also seems to require more resources and therefore higher server costs $$$ (good for cloud services I guess?) compared to v15. Server request patterns and performance should remain consistent (or improve) after upgrading. ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000 Available memory (MB): 65536 Available CPU cores: 10 Binaries: Node: 24.10.0 npm: 11.6.1 Yarn: 1.22.22 pnpm: N/A Relevant Packages: next: 15.5.5 // An outdated version detected (latest is 16.0.0), upgrade is highly recommended! eslint-config-next: N/A react: 19.1.1 react-dom: 19.1.1 typescript: 5.9.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Performance ### Which stage(s) are affected? (Select all that apply) Other (Deployed) ### Additional context The screenshot shows the ops/s after deploying v16 around 3:30 PM, I then proceeded to revert back my changes: <img width="1920" height="526" alt="Image" src="https://github.com/u
Comments (0)
No comments yet. Start the discussion.