Antoine du Hamel

> We could upgrade to 18.04, but that might take input from maintainers of the benchmarking work - is a jump in OS likely to have any meaningful impact on...

Thanks for the info, the script I was looking for is this one: https://github.com/nodejs/benchmarking/blob/master/experimental/benchmarks/community-benchmark/run.sh. The repo is read-only, I've asked in https://github.com/nodejs/TSC/issues/822#issuecomment-847717971 where we can move this script. > I've...

For some reason the benchmark involving http cannot even start on my machine, (probably some issue with my config), but I think @mcollina is able to run them on a...

> It's the `async_hooks` benchmarks that hang in https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1031/console Only the `async_hooks` benchmarks that involve http (`benchmark/async_hooks/async-resource-vs-destroy.js` and `benchmark/async_hooks/http-server.js`). I've noticed the same behaviour with `benchmark/http/cluster.js` and `benchmark/http/simple.js`.

Is there something I can do to help this move forward? I think upgrading to 20.04 would be a good first step, even if it doesn't solve the stalling issue.

@rvagg would it be possible for you to do the upgrade after the next v14.x release (scheduled on the 2021-07-27)? In case something wrong happen, it should give us more...

@rvagg now that the security release are out, would it be a good time for you to take care of the update? (No planned release until 2021-08-17 on nodejs/release repo)

Can we try to get back to that? I think we can upgrade straight to Ubuntu 22.04 now.

> @isaacs is working on PRs to move some packages into core. Being or not in the org changes nothing to that, right?

/cc @nodejs/build @nodejs/platform-windows for reviews