Gareth Ellis

This now seems to be working, and is ready for testing. @mcollina you mentioned you had some PRs to try it on. At the moment it is set to test...

Thoughts: currently its taking AGES to clone node core, What are thoughts on cloning once on the machine and then copying over to the workspace and doing a pull origin...

# How to: Running core benchmarks on Node.js CI ## Current function The current jenkins job aims at allowing the impact of a PR on a particular branch to be...

@AndreasMadsen @mcollina @mscdex , if you have some cycles do you want to have a go with the job, using instructions above and see how you get on? Also got...

Excellent - I will see what I can do about providing the raw data. Yes, we plan to get the info out to collaborators to start using, but thought it...

@mcollina , for getting to the raw data, if you click on your job, you should be able to open the workspace, and then browse to e.g. https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/ws/benchmarking/experimental/benchmarks/community-benchmark/node/output.csv. I'll modify...

OK, will look into that. In the meantime, csvs now get saved in the root of the ws with date/timestamp: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/ws/

the main reason was that we were using the default number set of iterations set per benchmark, I can add the RUNS parameter if you like, just need to appreciate...

@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...

I had a go at running the above benchmark, and also created a few other variants. I was interested how the above would be measuring shutdown as well as startup,...