You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a simple Next.js application with a single page. The page is dynamic and contains an await of 1000ms before showing content to the user.
Expected Behavior
By running clinic doctor --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start after the build, Doctor correctly recognize an issue in the cpu usage, suggesting to use Bulletproof to find the bottleneck.
Current Behavior
At this point, I try to run clinic bulletproof --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start and the analysis produces this graph. I'm not sure if that's the expected result, but it is not very helpful in identifying potential issues. I'm not sure if Bulletproof is just not the best tool for performing this type of analysis on Next.js or if this is an actual bug in the graph generation. I'll investigate a little bit
I created a simple Next.js application with a single page. The page is dynamic and contains an await of 1000ms before showing content to the user.
Expected Behavior
By running
clinic doctor --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start
after the build, Doctor correctly recognize an issue in the cpu usage, suggesting to use Bulletproof to find the bottleneck.Current Behavior
At this point, I try to run
clinic bulletproof --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start
and the analysis produces this graph. I'm not sure if that's the expected result, but it is not very helpful in identifying potential issues. I'm not sure if Bulletproof is just not the best tool for performing this type of analysis on Next.js or if this is an actual bug in the graph generation. I'll investigate a little bitSteps to Reproduce
npm run build
clinic bulletproof --autocannon [ / --method GET ] -- node ./node_modules/.bin/next start
Environment
The text was updated successfully, but these errors were encountered: