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-10-09 #244

Closed
mhdawson opened this issue Oct 3, 2018 · 5 comments
Closed

Node.js Foundation Benchmarking WorkGroup Meeting 2018-10-09 #244

mhdawson opened this issue Oct 3, 2018 · 5 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 3, 2018

Time

UTC Tue 09-Oct-2018 18:00 (06:00 PM):

Timezone Date/Time
US / Pacific Tue 09-Oct-2018 11:00 (11:00 AM)
US / Mountain Tue 09-Oct-2018 12:00 (12:00 PM)
US / Central Tue 09-Oct-2018 13:00 (01:00 PM)
US / Eastern Tue 09-Oct-2018 14:00 (02:00 PM)
London Tue 09-Oct-2018 19:00 (07:00 PM)
Amsterdam Tue 09-Oct-2018 20:00 (08:00 PM)
Moscow Tue 09-Oct-2018 21:00 (09:00 PM)
Chennai Tue 09-Oct-2018 23:30 (11:30 PM)
Hangzhou Wed 10-Oct-2018 02:00 (02:00 AM)
Tokyo Wed 10-Oct-2018 03:00 (03:00 AM)
Sydney Wed 10-Oct-2018 05:00 (05: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
  • Adding Node-DC-EIS micro-services workload to the benchmarks: input from @uttampawar on Node-DC-EIS #78
  • Adding npm workload to the benchmarks for the (new) Developer tooling: Node.js use case.
    • What should the workload be? npm install a laundry list of modules? Run through all of the npm commands?
    • To avoid network latency, I think it would be advisable to set up a local npm proxy like verdaccio. Thoughts?
  • Feedback on doc: update use cases and case coverage #243
  • Feedback on Candidate benchmarks #6 (any suggested workloads?)

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 Oct 3, 2018
@davisjam
Copy link
Contributor

davisjam commented Oct 3, 2018

Wish I could attend, but I'll be traveling to Node+JS Interactive.

Suggested additional items if there's time and interest:

  • Adding Node-DC-EIS micro-services workload to the benchmarks: input from @uttampawar on Node-DC-EIS #78
  • Adding npm workload to the benchmarks for the (new) Developer tooling: Node.js use case.
    • What should the workload be? npm install a laundry list of modules? Run through all of the npm commands?
    • To avoid network latency, I think it would be advisable to set up a local npm proxy like verdaccio. Thoughts?
  • Feedback on doc: update use cases and case coverage #243
  • Feedback on Candidate benchmarks #6 (any suggested workloads?)

@mhdawson
Copy link
Member Author

mhdawson commented Oct 3, 2018

I'm also going to be at Node+JS Interactive so I'm going to suggest we move out 1 week. Unfortunately, I'm busy at the 2EDT time slot but I could do 5EDT. @nodejs/benchmarking would that time work for people?

@mhdawson
Copy link
Member Author

mhdawson commented Oct 3, 2018

@davisjam all of those suggestions look like good additions to the agenda.

@davisjam
Copy link
Contributor

davisjam commented Oct 3, 2018

(FWIW 5EDT on 16 Oct. works for me.)

@mhdawson
Copy link
Member Author

mhdawson commented Oct 4, 2018

Going to move before I forget, For those who have not responded yet, if it does not work for you please comment here and we'll try to find a different time.

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

2 participants