Skip to content

Commit

Permalink
doc: remove benchmarking WG
Browse files Browse the repository at this point in the history
Benchmarking WG has been de-chartered, remove
references to it.

Refs: nodejs/TSC#955

Signed-off-by: Michael Dawson <mdawson@devrus.com>
  • Loading branch information
mhdawson committed Nov 27, 2020
1 parent 74a9272 commit 052c054
Showing 1 changed file with 0 additions and 18 deletions.
18 changes: 0 additions & 18 deletions locale/en/about/working-groups.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,6 @@ Core Working Groups are created by the
## Current Working Groups

* [Addon API](#addon-api)
* [Benchmarking](#benchmarking)
* [Build](#build)
* [Diagnostics](#diagnostics)
* [Docker](#docker)
Expand Down Expand Up @@ -48,23 +47,6 @@ Responsibilities include:
The current members can be found in their
[README](https://github.com/nodejs/nan#collaborators).

### [Benchmarking](https://github.com/nodejs/benchmarking)

The purpose of the Benchmark Working Group is to gain consensus
on an agreed set of benchmarks that can be used to:

* track and evangelize performance gains made between Node.js releases
* avoid performance regressions between releases

Responsibilities include:

* Identifying 1 or more benchmarks that reflect customer usage.
Likely will need more than one to cover typical Node.js use cases
including low-latency and high concurrency
* Working to get community consensus on the list chosen
* Adding regular execution of chosen benchmarks to Node.js builds
* Tracking/publicizing performance between builds/releases

### [Build](https://github.com/nodejs/build)

The Build Working Group's purpose is to create and maintain a distributed
Expand Down

0 comments on commit 052c054

Please sign in to comment.