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
$ # Download the test script and test file: https://github.com/quick-lint/bun-vs-node/tree/f5ca9314fde7432f8b20339b8380bb15203606af/bun-regexp-bug
$ git clone --depth=1 git@github.com:quick-lint/bun-vs-node.git
$ cd bun-vs-node/bun-regexp-bug/
$ node benchmark.mjs
263487 lines processed
took 201.37601999938488 ms
$ bun run benchmark.mjs
263487 lines processed
took 65417.94360200001 ms
What is the expected behavior?
Node.js and Bun have comparable performance. Maybe one is twice as fast as the other.
What do you see instead?
Bun is significantly slower than Node.js with this regexp.
Hi! I don't suppose it's possible to use https://github.com/google/re2 as a replacement to JSC's regex engine until the performance problems can be addressed?
Hi! I don't suppose it's possible to use https://github.com/google/re2 as a replacement to JSC's regex engine until the performance problems can be addressed?
i think no because it's not compatible with JS standarts. you can try to use node-re2
What version of Bun is running?
1.0.1
What platform is your computer?
Linux 5.19.0-46-generic x86_64 x86_64
What steps can reproduce the bug?
What is the expected behavior?
Node.js and Bun have comparable performance. Maybe one is twice as fast as the other.
What do you see instead?
Bun is significantly slower than Node.js with this regexp.
Additional information
Possibly related: #3464
The text was updated successfully, but these errors were encountered: