Repository navigation
Performance regression Date.toISOString() #47
Description
Activity
And it seems to be there since v19.3.0 (at least) https://github.com/RafaelGSS/nodejs-bench-operations/tree/main/v19.
Reacted by Vinicius Lourenço and Tony GorezWe updated to V8 10.8 in v19.3.0. Could this be related?
[c8421204b0] - deps: patch V8 to 10.8.168.21 (Michaël Zasso) nodejs/node#45749
No. This was caused by a semver-major change. I've adjusted the repository to run the benchmark against 18.0.0 and 19.0.0 and the regression is still there.
It's probably the update to V8 10.7
Implementation of toISOString was changed in v8/v8@126d477
Reacted by Toni Villena, Matteo Collina, Vinicius Lourenço and Marvin HagemeisterIs there an open issue in the V8 bug tracker for this?
Reacted by Toni Villena and Vinicius Lourençoprobably not
Is the regression still there with V8 11.3? @RafaelGSS
I don't think this is actionable?
Yeah, it's more of a tracking issue in case someone wants to fix it in the upstream.
These are the last results of
nodejs-bench-operationsand as you can see, toISOString might have been affected by a regression.