#Dev server slow

10 messages · Page 1 of 1 (latest)

stark forge
#

While deloping, it takes 1,5-2 sec. to update the page with the blank template which should be the most lightweight. Compare that to create-next-app which is <100 ms. I searched the whole web and I feel Like I'm the only one feeling the overhead. It's not from my PC. This is my repo. Could someone provide me with a minimal repo where the development server is snappy?

These are my PC specs

 pnpm payload info

> [email protected] payload C:\projects\real\payload-simple
> cross-env NODE_OPTIONS=--no-deprecation payload "info"


Binaries:
  Node: 23.11.0
  npm: N/A
  Yarn: N/A
  pnpm: 10.10.0
Relevant Packages:
  payload: 3.62.0
  next: 15.4.4
  @payloadcms/db-mongodb: 3.62.0      
  @payloadcms/email-nodemailer: 3.62.0
  @payloadcms/graphql: 3.62.0
  @payloadcms/next/utilities: 3.62.0  
  @payloadcms/payload-cloud: 3.62.0   
  @payloadcms/richtext-lexical: 3.62.0
  @payloadcms/translations: 3.62.0    
  @payloadcms/ui/shared: 3.62.0       
  react: 19.1.0
  react-dom: 19.1.0
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 32570        
  Available CPU cores: 8

GET / 200 in 2754ms
 GET / 200 in 756ms
 ✓ Compiled in 125ms
 ✓ Compiled / in 502ms
 GET / 200 in 2511ms
GitHub
GitHub - drago1520/bbh: Burgas Business Hub website

Burgas Business Hub website. Contribute to drago1520/bbh development by creating an account on GitHub.

full ospreyBOT
#
New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

Community-Help:

true crag
#

Try using this in your next.js config:

export default withPayload(nextConfig, { devBundleServerPackages: false })

stark forge
#

I did that already

stark forge
#

I've made real world tests for the speed. Github Repo. TLDR:

Official templates

Methodology

  1. I chaged the layout.tsx on all of the variants with a single letter.
  2. I used a stop timer by hand to measure from when I clicked to when I saw the letter on the screen. Not comprehensive per say, but 1000x better than nothing. This is real life benchmark for developers
  3. I haven't modified any code from pnpx create-payload-app@latest from 1 November 2025.
  4. I used pnpm dev with Node.js 23 on Windows 10 Intel Core i7-7820HQ 32GB RAM & Kingston SSD

Next.js 16 official

< 100 ms to see changes. Practically it was instant. Especially with the new fileSystemCache for dev turbo pack.

Blank (simple) template

It took 1-1.5 sec to see changes reflected on the UI. It was a good experience overall. Definitely things to be improved.

Website template

2,3-2,5 sec. I had to wait which loses my focus. People expect < 50ms for smth to happen. 2+ sec. and we get distracted. That's really bad.

Ecommerce

  • 5.41s; 4s; 3.4s; 4s; 3.50s; 4:49s (multiple chars). That's straight up slow. Really bad unusable experinece. The DX is out the window.

With Turbopack configured

Blank (simple)

Turbopack didn't help much. It's the same as without it.

Website

Turbopack didn't help much. It's the same as without it. 1.8-2 sec.

Ecommerce

3.5-4 sec. Not usable.

stark forge
#

I have a solution
basically started with a fresh Next 16 (suuuuper fast HMR)
and added payload gradually with create-payload-app. The whole day l've been extremely careful to preserve the DX of fast HMR and finally succeeded.
https://github.com/drago1520/payloadcms-speed-test-next16-from-scratch/tree/plain-next16-payloadcms
this one works. from 2-2.5 sec (unusable) HMR ->
~200ms (instant)
dockerized it also

GitHub
GitHub - drago1520/payloadcms-speed-test-next16-from-scratch at pla...

Contribute to drago1520/payloadcms-speed-test-next16-from-scratch development by creating an account on GitHub.

warm jasper
stark forge
#

omg, I have made it private. My bad.