Skip to content
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.

Commit

Permalink
doc: reflect Benchmarking WG is dechartered
Browse files Browse the repository at this point in the history
  • Loading branch information
mhdawson authored Nov 27, 2020
1 parent ad707ec commit 5986138
Showing 1 changed file with 2 additions and 41 deletions.
43 changes: 2 additions & 41 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,53 +1,14 @@
# Benchmarking Work Group

## Mandate
The benchmarking WG is now de-chartered and is no longer active.

The Benchmark working group's purpose is to gain consensus for an agreed set of benchmarks that can be used to:

1. Track and evangelize performance gains made between Node releases
2. Avoid performance regressions between releases

Its responsibilities are:

1. Identify 1 or more benchmarks that reflect customer usage. Likely need more than one to cover typical Node use cases including low-latency and high concurrency
2. Work to get community consensus on the list chosen
3. Add regular execution of chosen benchmarks to Node builds
4. Track/publicize performance between builds/releases

The path forward is to:
* Define the important
[use cases](https://github.com/nodejs/benchmarking/blob/master/docs/use_cases.md)
* Define the key
[runtime attributes](https://github.com/nodejs/benchmarking/blob/master/docs/runtime_attributes.md)
* Find/create benchmarks that provide good coverage for the
use cases and attributes
([current table](https://github.com/nodejs/benchmarking/blob/master/docs/use_cases.md))

See here for information about the infrastructure in place so far:
https://github.com/nodejs/benchmarking/blob/master/benchmarks/README.md

## Logistics

### Semi-monthly Meetings

Meetings of the working group typically occur every third Tuesday as shown on the
the node.js project [calendar](https://nodejs.org/calendar).
A few days before each meeting, an [issue](https://github.com/nodejs/benchmarking/issues)
will be created with the date and time of the meeting.
The issue will provide schedule logistics as well as
an agenda, links to meeting minutes, and
information about how to join as a participant or a viewer.

## Current Project Team Members
## Emeritus Project Team Members
+ Michael Dawson (@mhdawson) Facilitaor
+ Uttam Pawar (@uttampawar)
+ Michael Paulson (@michaelbpaulson)
+ Gareth Ellis (@gareth-ellis)
+ Kunal Pathak (@kunalspathak)
+ Jamie Davis (@davisjam)

## Emeritus Project Team Members

+ Trevor Norris (@trevnorris)
+ Ali Sheikh (@ofrobots)
+ Yosuke Furukawa (@yosuke-furukawa)
Expand Down

0 comments on commit 5986138

Please sign in to comment.