withastro / astro · Issue No. 18065

Dev server spends too much time to respond

Openby lumynou5opened Sep 18, 2026updated Sep 22, 202613 comments

triage: needs reproduction

Description

Astro Info

Astro                    v7.3.3
Node                     v22.17.1
System                   Linux (x64)
Package Manager          pnpm
Output                   static
Adapter                  @astrojs/cloudflare
Integrations             astro-icon

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

The dev server spends 4~12 s to respond some pages as per its log, but the browser doesn't actually receive the response when the log was printed. The browser usually loads the page in ~30 s.

The common attribute of those pages is that they use content collections. However, testing with the blog template can't reproduce the issue, so my guess is some changes in a newer revision broke the scalability since 7.0.3 version works fine. I checked out a commit before many contents are added, and it spends less time (though still too much), so it seems the issue is related to the scale.

What's the expected result?

It should work normally.

Link to Minimal Reproducible Example

N/A

Participation

I am willing to submit a pull request for this issue.

Relay Analysis

View on GitHub

Relay reads this issue against the repository's contribution signals: the files it is likely to touch, how the maintainers triage work this size, and what the first contribution would exercise.

The full analysis for this issue is still being assembled. Until then, the description above and the thread on GitHub are the most reliable context.