benchmarking
benchmarking copied to clipboard
nodejs
Node.js Benchmarking Working Group
Survey showed people don't know how to report issues: Some ideas 1) add link on Node.js org website 2) add info in benchmarking repo 3) add email address 4) Communication/publication
This was talked about in the feedback meeting, but https://github.com/v8/web-tooling-benchmark currently is only setup to test a minimal subset of workflows that do not use asynchronous tasks. That is the...
joyent/node PR https://github.com/joyent/node/pull/5187 proposed some new benchmarks for events that never landed. Not sure if it was ever reviewed. Going to close the PR there as it's not going to...
Continuing on from https://github.com/nodejs/node/pull/3962, this is an important metric for many users and we have no insight to it over time, at least nobody is tracking it as far as...
Since the PR was closed once I'd merged in my changes, I figured I'd open this to track current progress on getting this working. This is a continuation of #58...
I've been trying to benchmark Node-ChakraCore using the AcmeAir benchmark, and I'm getting a lot of noise in the throughput results. Is there any guidance on how to set up...
Opening this issue to track HTTP2 performance using simple metric obtained from dc-eis workload along with experimental branch/patch supporting http2 api.
As we are developing workloads/benchmarks to address wide range of use cases to measure performance, I would like to explore the idea of using these workloads/benchmarks not just by us...
The V8 team is looking to close the gap on ES.next vs ES5 performance, i.e. make ES2015 and beyond features as fast as their (naive) counterparts in ES5. There's a...
As suggested from https://github.com/nodejs/node/issues/11923#issuecomment-291286419 (where some performance regressions were found in v7.x)
