This repository has been archived by the owner on Nov 28, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 47
Benchmarking WG Meeting Aug 14 3 EST. #128
Comments
@nodejs/node please use emoji to indicate if you can make it or not. |
I can't make today. My main update is jenkins job is setup, would be good if people could give it a go. Take a look, if things aren't clear then shout up and I can write some clearer instructions. Likewise if there's a functional issue, then let me know. Currently the use-case that is setup is for evaluating impact of a PR on master. The second usecase to compare two commits, tags or branches is not setup yet, however it should be fairly trivial. I would suggest us adding a second Jenkins job for this to make it clearer to the end user. |
Just starting meeting now. |
Meeting live now. |
PR for minutes here: #135 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@nodejs/benchmarking
When
Monday Aug 14, 3 EST. (7PM UTC)
Where
link for participants: https://hangouts.google.com/hangouts/_/ytl/5tF9McB3cHrpKnlE8PpAIU-h9paHoi_S-zsFBniM9j0=?eid=100598160817214911030
For those who just want to watch: https://www.youtube.com/watch?v=vJLDtCU1L_M
youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled
Google doc for minutes: https://docs.google.com/document/d/1alcKNLeRMDI3RUdGqfGeEGI8mYMoeZmbnDV2YT7RsCU/edit
Agenda
Actions from last meeting
same variance of not.
Issues review
nodejs/benchmarking
Status of running node core benchmarks #127
New script to run Node-DC-EIS workload #123
The text was updated successfully, but these errors were encountered: