Skip to content

Conversation

@RafaelGSS
Copy link
Member

@RafaelGSS RafaelGSS commented Sep 11, 2025

According to nodejs/performance#186, HTTP benchmarks usually take a significant amount of time.

Leveraging nodejs/performance#80, I have decided to drop the test-double-http(s) benchmarkers as they aren't a reliable source of measurements. From now on, only Autocannon, Wrk and H2 (HTTP/2) are available for HTTP benchmarks.

I have also removed the http(s) benchmarks (http, http2, https) from the list of benchmark/run.js all as they deserve a separate namespace and to prevent the node-microbenchmark CI from taking a long time.

I will revamp the HTTP benchmarks from Node.js, and this is an initial step.

cc: @nodejs/performance

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/performance

@nodejs-github-bot nodejs-github-bot added benchmark Issues and PRs related to the benchmark subsystem. http Issues or PRs related to the http subsystem. http2 Issues or PRs related to the http2 subsystem. https Issues or PRs related to the https subsystem. performance Issues and PRs related to the performance of Node.js. labels Sep 11, 2025
Copy link
Member

@H4ad H4ad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Except from the lint issues, LGTM.

It would be great to see if @joyeecheung has any comments on this removal since she introduced it.

Also, maybe you should split the changes in two or more commits to clearly separate the changes (drop double benchmark, remove http benchs from run all)

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@RafaelGSS RafaelGSS force-pushed the refactor-http-benchmark branch from 850d07f to 600c564 Compare September 12, 2025 18:31
According to nodejs/performance#186,
HTTP benchmarks usually take a significant amount of time.

Leveraging nodejs/performance#80, I have
decided to drop the test-double-http(s) benchmarkers as they aren't
a reliable source of measurements. From now on, only Autocannon, Wrk
and H2 (HTTP/2) are available for HTTP benchmarks.

I have also removed the http(s) benchmarks (`http`, `http2`, `https`)
from the list of benchmark/run.js all as they deserve a separate
namespace and to prevent the node-microbenchmark CI from taking a long
time.

I will revamp the HTTP benchmarks from Node.js, and this is an initial
step.

Signed-off-by: RafaelGSS <[email protected]>
@RafaelGSS RafaelGSS force-pushed the refactor-http-benchmark branch from 600c564 to feacdc8 Compare September 12, 2025 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

benchmark Issues and PRs related to the benchmark subsystem. http Issues or PRs related to the http subsystem. http2 Issues or PRs related to the http2 subsystem. https Issues or PRs related to the https subsystem. performance Issues and PRs related to the performance of Node.js.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants