Following up on nodejs/node#59186 work.
Our benchmark suite takes a significant amount of time to conclude (85h for a full benchmark/compare). Most of the cases are because we are using an arbitrary n (number of iterations) in the benchmark, so it grows exponentially.
This issue is to keep tracking improvements from https://docs.google.com/spreadsheets/d/17iZuGR57r7ap4hFG8Tdz5Q-A7oV0cwM4MQW4q5bHA0U/edit?gid=2132828396#gid=2132828396
Following up on nodejs/node#59186 work.
Our benchmark suite takes a significant amount of time to conclude (85h for a full benchmark/compare). Most of the cases are because we are using an arbitrary
n(number of iterations) in the benchmark, so it grows exponentially.This issue is to keep tracking improvements from https://docs.google.com/spreadsheets/d/17iZuGR57r7ap4hFG8Tdz5Q-A7oV0cwM4MQW4q5bHA0U/edit?gid=2132828396#gid=2132828396