-
Notifications
You must be signed in to change notification settings - Fork 134
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 Technical Steering Committee (TSC) Meeting 2022-11-02 #1302
Comments
Lets also add this one to the agenda - nodejs/node#45223 |
@mcollina is there a question regarding nodejs/node#43658 or did we just forget to remove the |
It can be removed. Unfortunately the memory increase still remains. It's probably worthwhile for the TSC to be aware that this is coming and if they are comfortable with and addition 10-15MB of every worker thread created, as well as main process. |
We don’t yet know what the memory increase will be, as the PR isn’t working yet. The question will be whether the increase is worth the benefit of isolating loaders code from application code, and also of isolating loaders code from Node internals (preventing monkey-patching). It’s also very possible that the final implementation doesn’t spawn any worker threads when no user loaders are passed, which would mean that the memory increase is opt-in. |
Removed nodejs/node#43658 from agenda based on suggestion above. |
Startup performance:
|
PR for minutes - #1303 |
Time
UTC Wed 02-Nov-2022 15:00 (03:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/TSC
nodejs/i18n
nodejs/undici
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
tsc-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
Zoom link: https://zoom.us/j/611357642
Regular password
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: