mirror of https://github.com/sveltejs/svelte
chore: generate CPU profiles when running benchmarks (#18043)
This causes `pnpm bench` and `pnpm bench:compare` to generate `.cpuprofile` files for each benchmark, which should in theory make it easier to understand how different branches affect performance (and find opportunities for optimisation). These files can be opened directly in VS Code and other editors, or in [profiler.firefox.com](https://profiler.firefox.com), [speedscope.app](https://www.speedscope.app), Chrome's performance devtools and so on.pull/18045/head
parent
edcbb0e640
commit
99b1467ba4
Loading…
Reference in new issue