This repository was archived by the owner on Nov 28, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 28, 2020. It is now read-only.
Investigate the time taken, and number of benchmarks in core #225
Description
This is the starting place to begin running core benchmarks on a regular basis.
First steps: Put together a benchmark run that summarises time to run each suite as well as record number of results out of the run.
Then, at a future meeting: Look at results, decide on a subset to run on a regular basis that can fit into the time available and can be summarised appropriately.
Activity
gareth-ellis commentedon Jun 23, 2018
@mhdawson i'm writing a script to go through and collect the runtime for each core benchmark - could you create me a temporary job in jenkins I can modify and use to run this?
mhdawson commentedon Jun 25, 2018
Here you go https://ci.nodejs.org/job/benchmark-node-micro-benchmarks-gareth/
mhdawson commentedon Apr 16, 2019
Closing as we have not made progress. @gabrielschulhof is going to write a proposal for an alternate approach.
gabrielschulhof commentedon Sep 10, 2019
Spreadsheet tracking relative importance of benchmarks:
https://docs.google.com/spreadsheets/d/17ey-6r_sTVYpy6Zv0n55kqkVgqRf67aaf6Ub7eebGgo/edit#gid=0
gabrielschulhof commentedon Oct 2, 2019
... and the survey: https://docs.google.com/forms/d/1BlVwIYZPBBmR46Ru3okvddLiPj5Zy03XPE2kyW55VzQ/edit
gabrielschulhof commentedon Dec 3, 2019
Here's a spreadsheet with the processed responses where the benchmarks are sorted in order of popularity:
https://docs.google.com/spreadsheets/d/1_7VrAFO8K9KdQW8qEmnKnVBb514SMRqYiitoDu_cMiM/edit#gid=979605