|
| 1 | +# Node.js Performance Team Meeting 2023-05-29 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: https://www.youtube.com/watch?v=bqjXEyPQSfs |
| 6 | +* **GitHub Issue**: https://github.com/nodejs/performance/issues/85 |
| 7 | + |
| 8 | +## Present |
| 9 | + |
| 10 | +* Performance team: @nodejs/performance |
| 11 | +* Ulises Gascon: @ulisesgascon |
| 12 | +* Robert Nagy: @ronag |
| 13 | +* Vinícius Lourenço: @H4ad |
| 14 | +* Yagiz Nizipli: @anonrig |
| 15 | + |
| 16 | +## Agenda |
| 17 | + |
| 18 | +## Announcements |
| 19 | + |
| 20 | +*Extracted from **performance-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. |
| 21 | + |
| 22 | + |
| 23 | +* Libuv 1.45.0: https://github.com/nodejs/node/pull/48078 |
| 24 | + * Thanks to @bnoordhuis and https://github.com/isc-projects which iiuc sponsored some of his work. |
| 25 | + * It is providing a performance boost due the new Linux architecture |
| 26 | + |
| 27 | +* https://github.com/nodejs/performance/issues/85#issuecomment-1563757752 |
| 28 | + * Thanks to @kvakil: 30% boost at startup (v20.1.0 -> v20.2.0) |
| 29 | + |
| 30 | +* Yagiz is leaving for paternity leave. Ulises will help to host the next two meetings. |
| 31 | + |
| 32 | +### nodejs/performance |
| 33 | + |
| 34 | +* Performance of WHATWG ReadableStream.read() [#82](https://github.com/nodejs/performance/issues/82) |
| 35 | + * We are a little bit slower in comparison with Bun and Deno |
| 36 | + * It will be nice to see if Deno/Bun is using native implementation or JS. |
| 37 | +* Improve legacy CJS resolve #73 |
| 38 | + * The current approach is to use `simdjson` to perform the JSON parsing and increase the performance. See: https://github.com/nodejs/node/pull/47991 |
| 39 | + * @H4ad is working on this issue from now on |
| 40 | +* MakeCallback is very slow [#24](https://github.com/nodejs/performance/issues/24) |
| 41 | + * We reached out to more people about it, including the TSC meeting. |
| 42 | + * We need to do a deeper investigation |
| 43 | + * This approach made by the `uWebSockets.js` is interesting. See: https://github.com/nodejs/performance/issues/24#issuecomment-1559993286 |
| 44 | + * Daniel(@lemire) & Yagiz will work soon in a new library to resolve the Websockets layer (compatible with Node.js) |
| 45 | + |
| 46 | +* fetch [#11](https://github.com/nodejs/performance/issues/11) |
| 47 | + * No news, we will remove it from the agenda |
| 48 | + * Benchmarks and more info is needed before we can make any progress. |
| 49 | + * Contributions from the community are more than welcome here. |
| 50 | + |
| 51 | +## Q&A, Other |
| 52 | + |
| 53 | +* Expensive `isTraceHTTPEnable` (https://github.com/nodejs/performance/issues/81) is worth mentioning. @H4ad is working on it. |
| 54 | +* Vinícius is nominated/invited to the Performance Team. Reference: https://github.com/nodejs/performance/issues/86 |
| 55 | + |
| 56 | +## Upcoming Meetings |
| 57 | + |
| 58 | +* **Node.js Foundation Calendar**: https://nodejs.org/calendar |
| 59 | + |
| 60 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
| 61 | + |
0 commit comments