Reading trace.log files from turbopack (next dev is slow for us)
Unanswered
Xoloitzcuintli posted this in #help-forum
XoloitzcuintliOP
Hey everyone,
We're encountering slow dev mode performance in our Next.js application and, after investigating, we started generating trace and trace.log files to pinpoint where the compiler is spending most of its time.
Before reaching out to the core team, I wanted to ask if there's a way to read or visualize the trace.log file to better understand what's happening. (Jaegger does not seem to accept the trace.log file)
For context, we've already reduced the initial page compile time from ~15s to around 6-7 seconds by compiling barrel TS files from other pnpm workspaces we depend on and by leveraging optimizePackageImports.
Any suggestions on what the next step could be?
We're encountering slow dev mode performance in our Next.js application and, after investigating, we started generating trace and trace.log files to pinpoint where the compiler is spending most of its time.
Before reaching out to the core team, I wanted to ask if there's a way to read or visualize the trace.log file to better understand what's happening. (Jaegger does not seem to accept the trace.log file)
For context, we've already reduced the initial page compile time from ~15s to around 6-7 seconds by compiling barrel TS files from other pnpm workspaces we depend on and by leveraging optimizePackageImports.
Any suggestions on what the next step could be?