16 Oct 2018
Google Form for Questions: https://docs.google.com/forms/d/e/1FAIpQLSea-eYU11_GYrJJCAXPX7hUM-CWsDPgTdFt0Xse64OzU0OHRA/viewform
- 4 participants
- 42 minutes
18 Sep 2018
https://github.com/nodejs/user-feedback/issues/90
September Node.js Online Meetup organized by the Node.js User Feedback team.
Schedule:
* 5pm ET - Gather and socialize
* 5:30pm to 6:30pm ET - Talks
* 6:30pm to 7:00pm - Open discussion
Talks:
* Michael Dawson, Node.js TSC Chair and CommCom Member - @mhdawson
* Rich Trott, Node.js TSC - @trott
Talk 1:
Introduction to Node.js Initiatives, working groups and teams and how to get involved
with Michael Dawson
Get to know the Node.js initiatives, working groups and teams (including Community Committee and TSC initiatives) and how to get involved.
Talk 2:
A Response To “Design Mistakes in Node”
with Rich Trott
What should we do about design mistakes in Node.js? A non-inflammatory (I promise!) review and response to an event that prompted headlines like "Node.js Creator Blasts Node.js".
September Node.js Online Meetup organized by the Node.js User Feedback team.
Schedule:
* 5pm ET - Gather and socialize
* 5:30pm to 6:30pm ET - Talks
* 6:30pm to 7:00pm - Open discussion
Talks:
* Michael Dawson, Node.js TSC Chair and CommCom Member - @mhdawson
* Rich Trott, Node.js TSC - @trott
Talk 1:
Introduction to Node.js Initiatives, working groups and teams and how to get involved
with Michael Dawson
Get to know the Node.js initiatives, working groups and teams (including Community Committee and TSC initiatives) and how to get involved.
Talk 2:
A Response To “Design Mistakes in Node”
with Rich Trott
What should we do about design mistakes in Node.js? A non-inflammatory (I promise!) review and response to an event that prompted headlines like "Node.js Creator Blasts Node.js".
- 4 participants
- 44 minutes
29 Jan 2018
- 10 participants
- 56 minutes
9 Mar 2017
Node.js Community Benchmarking Efforts - Gareth Ellis, IBM
Benchmarks and the information they provide are important to ensure that changes going into Node.js don’t regress key attributes like startup speed, memory footprint and throughput. Come and hear about some of the fundamentals of benchmarking, how to go about narrowing down the cause of a regression between versions of node along with the efforts underway in the community benchmarking workgroup (https://github.com/nodejs/benchmarking) to run/capture/report and act on benchmark information.
Benchmarks and the information they provide are important to ensure that changes going into Node.js don’t regress key attributes like startup speed, memory footprint and throughput. Come and hear about some of the fundamentals of benchmarking, how to go about narrowing down the cause of a regression between versions of node along with the efforts underway in the community benchmarking workgroup (https://github.com/nodejs/benchmarking) to run/capture/report and act on benchmark information.
- 1 participant
- 22 minutes
15 Dec 2016
Node.js Community Benchmarking Efforts - Michael Dawson, IBM
Benchmarks and the information they provide are important to ensure that changes going into Node.js don't regress key attributes like startup speed, memory footprint and throughput. Come and hear about some of the fundamentals of benchmarking, how to go about narrowing down the cause of a regression between versions of node along with the efforts underway in the community benchmarking workgroup (https://github.com/nodejs/benchmarking) to run/capture/report and act on benchmark information.
About Michael Dawson
Michael Dawson is an active contributor to Node.js as a CTC member, the facilitator for the benchmarking working group, participant in the lts, build, api and port-mortem working groups and has contributed many of the changes to enable support for Linux on Power, LinuxOne and AIX. He leads the Node.js team within IBM’s runtime technologies team driving IBM’s Node.js runtime deliveries and the runtime team’s contribution to Node.js and v8 within the Node and google communities. He’s been working in the industry for over 25 years with the last 11 focused on building runtimes including Node.js and Java. Further back, he held leadership roles in teams that developed e-commerce applications and delivered them as services, including EDI communication services, credit card processing and electronic invoicing.
Benchmarks and the information they provide are important to ensure that changes going into Node.js don't regress key attributes like startup speed, memory footprint and throughput. Come and hear about some of the fundamentals of benchmarking, how to go about narrowing down the cause of a regression between versions of node along with the efforts underway in the community benchmarking workgroup (https://github.com/nodejs/benchmarking) to run/capture/report and act on benchmark information.
About Michael Dawson
Michael Dawson is an active contributor to Node.js as a CTC member, the facilitator for the benchmarking working group, participant in the lts, build, api and port-mortem working groups and has contributed many of the changes to enable support for Linux on Power, LinuxOne and AIX. He leads the Node.js team within IBM’s runtime technologies team driving IBM’s Node.js runtime deliveries and the runtime team’s contribution to Node.js and v8 within the Node and google communities. He’s been working in the industry for over 25 years with the last 11 focused on building runtimes including Node.js and Java. Further back, he held leadership roles in teams that developed e-commerce applications and delivered them as services, including EDI communication services, credit card processing and electronic invoicing.
- 4 participants
- 21 minutes
18 Nov 2016
Node.js benchmarking WG meeting -https://github.com/nodejs/benchmarking/issues/69
- 6 participants
- 31 minutes
21 Apr 2016
Gareth Ellis is a part of Node.js benchmarking working group: https://github.com/nodejs/benchmarking.
In this video, he provides an introduction to benchmarking, how to get started with benchmarking (depending on what you are looking to test), key challenges to benchmarking, approaches to benchmarking, benchmarking Node.js, and use cases.
Gareth's GitHub page is here: https://github.com/gareth-ellis.
Thank you to Opbeat for sponsoring the videos for Node.js Live Paris, and IBM for sponsoring the Node.js Live Paris event.
In this video, he provides an introduction to benchmarking, how to get started with benchmarking (depending on what you are looking to test), key challenges to benchmarking, approaches to benchmarking, benchmarking Node.js, and use cases.
Gareth's GitHub page is here: https://github.com/gareth-ellis.
Thank you to Opbeat for sponsoring the videos for Node.js Live Paris, and IBM for sponsoring the Node.js Live Paris event.
- 1 participant
- 22 minutes
