Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js Foundation Benchmarking WorkGroup Meeting 2017-11-20 #23

Closed
mhdawson opened this issue Nov 17, 2017 · 0 comments
Closed

Node.js Foundation Benchmarking WorkGroup Meeting 2017-11-20 #23

mhdawson opened this issue Nov 17, 2017 · 0 comments
Assignees

Comments

@mhdawson
Copy link
Owner

Time

UTC Mon 20-Nov-2017 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Mon 20-Nov-2017 12:00 (12:00 PM)
US / Mountain Mon 20-Nov-2017 13:00 (01:00 PM)
US / Central Mon 20-Nov-2017 14:00 (02:00 PM)
US / Eastern Mon 20-Nov-2017 15:00 (03:00 PM)
Amsterdam Mon 20-Nov-2017 21:00 (09:00 PM)
Moscow Mon 20-Nov-2017 23:00 (11:00 PM)
Chennai Tue 21-Nov-2017 01:30 (01:30 AM)
Hangzhou Tue 21-Nov-2017 04:00 (04:00 AM)
Tokyo Tue 21-Nov-2017 05:00 (05:00 AM)
Sydney Tue 21-Nov-2017 07:00 (07:00 AM)

Or in your local time:

Links

Agenda

Extracted from Benchmarking-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/benchmarking

  • Add Ghost.js workload to the benchmarking #159
  • Survey questions for end users to decide what to benchmark #136
  • Status of running node core benchmarks #127

Invited

  • Benchmarking team: @nodejs2/benchmarking

Observers

Notes

The agenda comes from issues labelled with Benchmarking-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

@mhdawson mhdawson self-assigned this Nov 17, 2017
@mhdawson mhdawson closed this as completed Apr 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant