#How to profile and optimize?
8 messages · Page 1 of 1 (latest)
you can use --inspect flag and use Chrome Devtools' built-in Profiler
I recommend inspect-brk over the regular inspect because of the fact that it will wait for input from chromium.
Other than profiling its also a good thing to have benchmarks so verify your changes actually made a impact and by what
or brand new --inspect-wait , it won't break on the first line 😛
Oh I'm a perf nerd and I didn't even know that one lol
What makes it different to brk?
waits for inspector to connect and runs code (doesn't place a breakpoint)