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 Performance Team Meeting 2023-04-03 #68

Closed
mhdawson opened this issue Mar 29, 2023 · 0 comments · Fixed by #69
Closed

Node.js Performance Team Meeting 2023-04-03 #68

mhdawson opened this issue Mar 29, 2023 · 0 comments · Fixed by #69
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Mon 03-Apr-2023 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Mon 03-Apr-2023 10:00 (10:00 AM)
US / Mountain Mon 03-Apr-2023 11:00 (11:00 AM)
US / Central Mon 03-Apr-2023 12:00 (12:00 PM)
US / Eastern Mon 03-Apr-2023 13:00 (01:00 PM)
EU / Western Mon 03-Apr-2023 18:00 (06:00 PM)
EU / Central Mon 03-Apr-2023 19:00 (07:00 PM)
EU / Eastern Mon 03-Apr-2023 20:00 (08:00 PM)
Moscow Mon 03-Apr-2023 20:00 (08:00 PM)
Chennai Mon 03-Apr-2023 22:30 (10:30 PM)
Hangzhou Tue 04-Apr-2023 01:00 (01:00 AM)
Tokyo Tue 04-Apr-2023 02:00 (02:00 AM)
Sydney Tue 04-Apr-2023 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

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

nodejs/performance

  • add/remove handlers are slow on EventTarget #60
  • Bun & Deno Comparision #55
  • AbortSignal pattern is slow #44
  • Module resolution #39
  • EventTarget #32
  • fetch #11

Invited

  • Performance team: @nodejs/performance

Observers/Guests

Notes

The agenda comes from issues labelled with performance-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

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

Successfully merging a pull request may close this issue.

1 participant