@@ -27,6 +27,8 @@ back in to the TSC.
27
27
* [ Roadmap] ( #roadmap )
28
28
* [ Docker] ( #docker )
29
29
* [ Addon API] ( #addon-api )
30
+ * [ Benchmarking] ( #benchmarking )
31
+ * [ Post-mortem] ( #post-mortem )
30
32
* [ Starting a Working Group] ( #starting-a-wg )
31
33
* [ Bootstrap Governance] ( #bootstrap-governance )
32
34
* [ Intl] ( #Intl )
@@ -219,6 +221,38 @@ Their responsibilities are:
219
221
The current members can be found in their
220
222
[ README] ( https://github.com/nodejs/nan#collaborators ) .
221
223
224
+ ### [ Benchmarking] ( https://github.com/nodejs/benchmarking )
225
+
226
+ The purpose of the Benchmark working group is to gain consensus
227
+ for an agreed set of benchmarks that can be used to:
228
+
229
+ + track and evangelize performance gains made between Node releases
230
+ + avoid performance regressions between releases
231
+
232
+ Its responsibilities are:
233
+
234
+ + Identify 1 or more benchmarks that reflect customer usage.
235
+ Likely need more than one to cover typical Node use cases
236
+ including low-latency and high concurrency
237
+ + Work to get community consensus on the list chosen
238
+ + Add regular execution of chosen benchmarks to Node builds
239
+ + Track/publicize performance between builds/releases
240
+
241
+ ### [ Post-mortem] ( https://github.com/nodejs/post-mortem )
242
+
243
+ The Post-mortem Diagnostics working group is dedicated to the support
244
+ and improvement of postmortem debugging for Node.js. It seeks to
245
+ elevate the role of postmortem debugging for Node, to assist in the
246
+ development of techniques and tools, and to make techniques and tools
247
+ known and available to Node.js users.
248
+
249
+ Its responsibilities are:
250
+
251
+ + Defining and adding interfaces/APIs in order to allow dumps
252
+ to be generated when needed
253
+ + Defining and adding common structures to the dumps generated
254
+ in order to support tools that want to introspect those dumps
255
+
222
256
## Starting a WG
223
257
224
258
A Working Group is established by first defining a charter that can be
0 commit comments