Interpreting Turbopack Traces
Unanswered
Morelet’s Crocodile posted this in #help-forum
Morelet’s CrocodileOP
I'm trying to identify bottlenecks in my dev mode performance by inspecting my Turbopack trace, but I can't find any resources on what to look for. I'm searching for tips like "this step should be 30-40% of compilation", or "look out for long running [blank] steps", etc. Does anyone know of a resource like this? If not, what do you look for when interpreting a trace?
I'll leave a screenshot of my trace here in case someone's interested in diagnosing.
I'll leave a screenshot of my trace here in case someone's interested in diagnosing.