3 ms·

I haven't confirmed it with hard numbers yet, but I think these perf regressions may also be affecting node; node 13.1 executes our test suite in about 5 minute

I haven't confirmed it with hard numbers yet, but I think these perf regressions may also be affecting node; node 13.1 executes our test suite in about 5 minutes on my workstation, while a canary build of node running the latest v8 (which I was trying because it fixed a perf regression in debug stepping performance which first appears in node 13.2) seems to take almost 7 minutes. Now, I thought it was just maybe a consequence of it being a prerelease build; but seeing this, if it's actually just indicative of broad perf regressions in v8... I'll be honest, I'd be surprised, since every v8 release blog is always talking about perf _improvements_.

vbezhenar 7y ago
If it's important for you, you can try to find commit which degrades performance by using bisect.
leeoniya 7y ago
> while a canary build of node running the latest v8 keep in mind that canary builds might not be compiled with all the typical release optimization flags turned on.