Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix too slow [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#86275•Fetched 2026-04-08 02:11:44
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
DanhezCodeDanhezCode
Participants
DanhezCodeDanhezCodegithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Root Cause

I used AutoCanon to measure the results of a project started from scratch with nothing added to the home directory created by you, which is completely static. How is it possible that it serves less than 2k requests per second when it only serves them because it was already generated at build time and is completely static?

Code Example

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
  Available memory (MB): 16248
  Available CPU cores: 4
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.22.0
Relevant Packages:
  next: 16.0.3 // Latest available version is detected (16.0.3).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: N/A
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/vercel/next.js/tree/canary/examples/hello-world

To Reproduce

I used AutoCanon to measure the results of a project started from scratch with nothing added to the home directory created by you, which is completely static. How is it possible that it serves less than 2k requests per second when it only serves them because it was already generated at build time and is completely static?

Current vs. Expected behavior

Current behavior less than 2k, expected at least above 5k for something static

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
  Available memory (MB): 16248
  Available CPU cores: 4
Binaries:
  Node: 24.11.1
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.22.0
Relevant Packages:
  next: 16.0.3 // Latest available version is detected (16.0.3).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: N/A
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)

next start (local)

Additional context

<img width="1310" height="734" alt="Image" src="https://github.com/user-attachments/assets/f97b90c0-0ca0-4b6c-977a-7c450173e1a6" />

extent analysis

TL;DR

  • Investigate and optimize server configuration and environment to improve performance of serving static content.

Guidance

  • Review the Next.js configuration and server settings to ensure they are optimized for serving static content.
  • Verify that the static files are being served directly by the server without unnecessary processing or rendering.
  • Check the system resources (CPU, memory, and network) to ensure they are not bottlenecking the server's performance.
  • Consider using a load testing tool to simulate a larger number of requests and identify potential performance bottlenecks.

Example

No specific code example is provided as the issue seems to be related to server configuration and performance rather than a specific code snippet.

Notes

The provided information suggests that the issue is related to the performance of serving static content, but the root cause is unclear. Further investigation is needed to determine the exact cause of the performance bottleneck.

Recommendation

  • Apply workaround: Optimize server configuration and environment for better performance, as the current version of Next.js (16.0.3) does not seem to be the primary cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#GPU compatibility#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix too slow [1 comments, 2 participants]