lukechilds/node - node - Gitea: Git with a cup of tea

Tree: 0f4c7b8c37

Rich Trott ef6a5cf40a benchmark: split timers benchmark and refactor The depth benchmark for timers sets a timer that sets a timer that sets a timer that... 500K of them. Since each timer has to wait for the next tick of the event loop this benchmark takes a very long time to run compared to the breadth test that is already in the file. This may be more of an event loop benchmark than a timer benchmark. Reduce the number of iterations for the depth test as it's really just running the iterations in sequence, not in parallel. And even on an infinitely fast machine, it would take over 8 minutes to run because each tick of the event loop would have to wait 1ms before firing the timer. Split the depth and breadth benchmarks so that their `N` values can be set independently. Do some minor refactoring to the benchmarks (but no ES6 additions so that the benchmarks can still be run with old versions of Node.js). Refs: https://github.com/nodejs/node/issues/9493 PR-URL: https://github.com/nodejs/node/pull/9497 Reviewed-By: Andreas Madsen <amwebdk@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>		8 years ago
..
immediate.js	benchmark: add `setImmediate()` benchmarks	9 years ago
timers-breadth.js	benchmark: split timers benchmark and refactor	8 years ago
timers-depth.js	benchmark: split timers benchmark and refactor	8 years ago