Next.js Discord

Discord Forum

Next.js with Turbopack Extremely Slow on Mac M1 (Over 50s for Simple Routes)

Unanswered
AM posted this in #help-forum
Open in Discord
AMOP
Hey folks, I'm running into an issue where Next.js dev mode is extremely slow to compile, even for basic API routes.

- I'm on a MacBook Air M1, and using other frameworks like Vite, Vue, and Angular works totally fine—super fast.
- But with Next.js and Turbopack, it becomes painfully slow.
Here’s my setup:
"next": "^15.3.3",
"dev": "next dev --turbopack",
node -v => v22.13.1


Example log:

GET /gigs 200 in 53034ms
POST /gigs 200 in 10125ms
HEAD /gigs 200 in 11357ms
Compiling /api/activities ...


This is unbelievably slow. Has anyone experienced similar issues on Apple Silicon or with Turbopack? Any ideas what might be causing it?

30 Replies

before, run it without --turbopack flag and see if its still slow
@Dutch i would like to investigate it, can you give me a live share link to check it
AMOP
hey brok1 👋 , testing ASAP without --turbopack, live is running 10/10 it's only dev problem :X
@AM hey brok1 👋 , testing ASAP without --turbopack, live is running 10/10 it's only dev problem :X
Dutch
heard that turbopack has problems with some of cpu archs, maybe yours is kinda not enough to handle it
i had same problems years ago and only solution was upgrading my hardware for me
AMOP
pfff. yeah def much faster

so initial load, trying on dummy page took about 21s
 POST /privacy-policy 200 in 21014ms
 POST /privacy-policy 200 in 822ms


but after that navigation to other pages is much faster less than 10s ( depends on the page ) for initial visit


Non initial load:
 GET /gigs 200 in 9159ms
bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)
 POST /gigs 200 in 763ms
 POST /gigs 200 in 162ms
 POST /gigs 200 in 165ms
 POST /gigs 200 in 212ms
 POST /gigs 200 in 472ms
 POST /gigs 200 in 431ms


INitial load:
POST /gigs 200 in 24051ms
 GET /gigs 200 in 24115ms
 POST /gigs 200 in 2369ms
 HEAD /gigs 200 in 194ms
 POST /gigs 200 in 1205ms
 POST /gigs 200 in 346ms
 POST /gigs 200 in 184ms


With turbopack initial load:

GET /gigs 200 in 53034ms
POST /gigs 200 in 10125ms
HEAD /gigs 200 in 11357ms
@Dutch i had same problems years ago and only solution was upgrading my hardware for me
AMOP
yeah at some point today i went crazy I was 3 mins away from going out and buy new macbook
@AM yeah at some point today i went crazy I was 3 mins away from going out and buy new macbook
Dutch
turbopack is not giving much benefit, i mean if you cant upgrade or dont want to do, your system you know
2s initial load is okay
to make you feel better, here is my stats, with turbopack 
 ✓ Starting...
 ✓ Ready in 975ms
 ○ Compiling / ...
 ✓ Compiled / in 1024ms
 GET / 200 in 1190ms
 ✓ Compiled /favicon.ico in 206ms
 GET /favicon.ico?favicon.e79dd557.ico 200 in 471ms
 ○ Compiling /siparis ...
 ✓ Compiled /siparis in 504ms
 GET /siparis 200 in 538ms
it has heavy and variant modules inside, so its taking up some time to load
also if matters, you can remove node_modules, .next, package-lock.json and reinstall everything again to check
@Dutch 2s initial load is okay
AMOP
20* 😄
but when its 2x better looks even faster lol
@AM 20* 😄
Dutch
can you share same logs with me, to see its initial load times
cuz your pages can be so large to load and your api queries can be slow. sorry i had so much failures so far 😄
and things i told above are totally reasons to make someone sad enough, i have long conversational issues on their github s
let me find
○ Compiling /tasks ...
✓ Compiled in 39.9s (sometimes around 60)
✓ Compiled /tasks in 18.2s
my famous last words:
Well I tried even next 15@rc and without turbo, still my dev server takes around 1gb memory and takes near minutes to compile.
I am not using turbopack at all. But i understand what is problem though, had to upgrade my hardware and problem solved for 2000$ 😂 . Thanks for your all effort
@AM yeah here they are: https://discord.com/channels/752553802359505017/1392501049893322773/1392515761888825424
Dutch
Not that, that lines with starting, ready, compiling etc
@Dutch Not that, that lines with starting, ready, compiling etc
AMOP
those?

andonmitev@MacBookAir gigbot % pnpm dev

> fc-client@0.1.0 dev /Users/andonmitev/Desktop/gigbot
> next dev

✔ Console Ninja extension is connected to Next.js, see https://tinyurl.com/2vt8jxzw
   ▲ Next.js 15.3.3
   - Local:        http://localhost:3000
   - Network:      http://127.94.0.1:3000
   - Environments: .env.local

 ✓ Starting...
 ✓ Ready in 2.9s
 ✓ Compiled /middleware in 281ms (109 modules)
 ○ Compiling /gigs ...
 ✓ Compiled /gigs in 22s (17422 modules)
POST /gigs 200 in 26955ms
 GET /gigs 200 in 26205ms
bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)
 HEAD /gigs 200 in 874ms
 POST /gigs 200 in 6660ms
 POST /gigs 200 in 1059ms
 POST /gigs 200 in 182ms
🤔
AMOP
it's private and quite a lot setup
but thank you so much 😄
either way i would purchase a new mac but waiting for the latest models to be dropped in a few months
@AM either way i would purchase a new mac but waiting for the latest models to be dropped in a few months
Dutch
Also can be your files are too much big to parse
Looks like POST /gigs 26sec