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

Node.js Foundation Benchmarking WorkGroup Meeting 2018-08-13 #236

Closed
mhdawson opened this issue Aug 8, 2018 · 7 comments
Closed

Node.js Foundation Benchmarking WorkGroup Meeting 2018-08-13 #236

mhdawson opened this issue Aug 8, 2018 · 7 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Aug 8, 2018

Time

UTC Mon 13-Aug-2018 18:00 (06:00 PM):

Timezone Date/Time
US / Pacific Mon 13-Aug-2018 11:00 (11:00 AM)
US / Mountain Mon 13-Aug-2018 12:00 (12:00 PM)
US / Central Mon 13-Aug-2018 13:00 (01:00 PM)
US / Eastern Mon 13-Aug-2018 14:00 (02:00 PM)
London Mon 13-Aug-2018 19:00 (07:00 PM)
Amsterdam Mon 13-Aug-2018 20:00 (08:00 PM)
Moscow Mon 13-Aug-2018 21:00 (09:00 PM)
Chennai Mon 13-Aug-2018 23:30 (11:30 PM)
Hangzhou Tue 14-Aug-2018 02:00 (02:00 AM)
Tokyo Tue 14-Aug-2018 03:00 (03:00 AM)
Sydney Tue 14-Aug-2018 04:00 (04: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

  • Investigate the time taken, and number of benchmarks in core #225
  • Require cached pref much lower #202
  • Add Ghost.js workload to the benchmarking #159

Invited

  • Benchmarking team: @nodejs/benchmarking

Observers/Guests

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 Aug 8, 2018
@uttampawar
Copy link
Contributor

+1

@gareth-ellis
Copy link
Member

I'm not going to be able to make it tonight, I'm afraid

@BridgeAR
Copy link
Member

I would like to join. Especially about #225. It says the host did not yet start the meeting?

@uttampawar
Copy link
Contributor

@BridgeAR I'm waiting as well. Looks like @mhdawson needs to join since he is the host.

@BridgeAR
Copy link
Member

I guess we should set up a new date in this case?

@mhdawson
Copy link
Member Author

Sorry I was away on vacation and the meeting was generated after I left.

@gareth-ellis, @BridgeAR @uttampawar looks like the next regularly scheduled meeting is Aug 28th which is next week so I'll suggest we'll wait until then.

@mhdawson
Copy link
Member Author

closing since next meeting happened.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants