-
Notifications
You must be signed in to change notification settings - Fork 47
Meeting at NodeConf EU '17 to discuss Node.js performance #124
Comments
If we want this conversation happening, I think we can make a room available for the meeting. |
@jaro-sevcik from the V8 compiler team is also going to join. |
I'm going to be at NodeConfEU and Arunesh will be there but none of the other benchmarking WG members will be that we know of. Node Interactive might be better but those on the last call are still not sure. I'm thinking we should set up an on-line meeting to get started on discussion. I'm out next week so how about we send out a doodle for the week of Aug 21st. |
I'm on vacation that week, but maybe we can do it the week after? |
People who are interested, please share your availability in week of August 28th at https://doodle.com/poll/byewa29dzkmx8xf3 |
Thanks for setting up the Doodle. Unfortunately none of the time slots work for me currently. |
What are the times you are available? I will include those as well in the doodle. |
How about adding 6AM / 9AM / 11AM Europe/Berlin to the Doodle? |
Updated. |
@bmeurer any chance you could make the next regular benchmarking meeting which is August 28 at 3 EST, 7 UTC ? It would be good to get some of you as regular attendees for the benchmarking WG meetings. |
I guess so, yes. Is that 8:00 CET or 20:00 CET? |
21:00 CET (CET is currently UTC+2) |
Ok, I'll join tomorrow. What's the Hangout id? |
@bmeurer hangout id has been added to the issue for the meeting. Sorry I just opened it today. It is: |
Thanks. |
@bmeurer is now attending our bi-weekly meeting so I think we can close this. Please let me know if that is not the case. |
I'd like to propose some kind of informal meeting at NodeConf EU in November to discuss various aspects of Node.js performance, specially how to track performance and how to prioritize potential work items. One of the main items here is obviously the need for benchmarks, ideally a standardized benchmark suite that is representative of common JavaScript workloads on the Node.js side.
Background here is that for V8 it's currently difficult to properly include Node.js concerns when it comes to planning around performance optimizations. Similarly the lack of a standard benchmark suite made it difficult for Node.js to decide on whether or not to use a certain V8 version for a given Node.js release (as we've experienced with Node 8 and V8 5.8 to 6.1 now). Being able to plan in advance and properly include important concerns for Node.js use cases would reduce the pain for everyone significantly, and I think an in-person meeting would help a lot here.
I'll be at NodeConf EU together with @psmarshall, who's been working a lot on Node.js performance recently.
The text was updated successfully, but these errors were encountered: