Add benchmarks for native NodeJS (LTS) server?

[prescience-data]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

I might be misreading one of the existing labels which perhaps already provides this benchmark, but it would be great to get a benchmark for the native (LTS) NodeJS node:http server class.

Motivation

This would help when justifying the use of Fastify to stakeholders when presented with the "why not native?" question where native may be a reasonable option when provided the context of a performance differential.

Currently, I find myself leaning too heavily on "because we might need additional features in the future", which feels weak from a justification perspective, without knowing how much more (or less) performance might be gained from implementing the native server instead.

Example

An example would be when planning a small, simple http or websocket server for an internal application.

It's unknown or unlikely if more advanced features might be required in the future, but refactoring to Fastify in the event this occurs would be expensive.

Although certainly not the only factor within the decision matrix, the performance differential (especially if the result is better-than-native) would be a key consideration when calculating a cost/benefit EV of the comparison.

[prescience-data]

Edit - after reading a blog regarding the Fastify benchmarks, is it correct to understand that "bare" is the native server?

source

If so, perhaps making this more explicit in the results table might be helpful for some as this wasn't immediately clear to me?

[mcollina]

Yes, bare is the native http server. Would you like to make a PR to keep this clearer?

[prescience-data]

Yep will do that - I think just a minimal "(Node 14.x.x)" suffix should be enough if that sounds ok?

(I assume from reading the main page, this is the version used in the current benchmark?)

[mcollina]

I think that might be off too, check what versions the benchmarks are actually run. You can bring it up to v18.

[prescience-data]

This is the correct entrypoint to the generator that produces the markdown yeah?
https://github.com/fastify/benchmarks/blob/master/lib/packages.js

[climba03003]

Here is the actual version running against the benchmark.

benchmarks/.github/workflows/benchmarks.yml

Line 21 in da0b992

node-version: 14

This is the correct entrypoint to the generator that produces the markdown yeah?

Yes, you can update the static version to process.version.

benchmarks/lib/packages.js

Line 7 in da0b992

bare: { version: '10.13.0' },

[mcollina]

Note that we should also update this to node v18

[Fdawgs]

Maybe rename base to node:http?