Replies: 2 comments
-
That would be great. Feel free to create benchmarks using the Vitest bench or any other approach that works for you. For every perf improvement, it’ll be great to see concrete number for the ops/sec. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Agreed! Maybe we should consider setting up a ci structure for this to catch potential regressions? That might be a bit above my paygrade, though 🙃 Being able to perf-test this against actual browsers (playwright, maybe) as well as against node would be great. AFAIK the vitest bench only targets node. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! I'm interesting in doing some perf work on the codebase, but there doesn't seem to be too many benchmarking tests at the time of writing. Is this something you've discussed internally?
Beta Was this translation helpful? Give feedback.
All reactions