-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
Closed
Labels
libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.performanceIssues and PRs related to the performance of Node.js.Issues and PRs related to the performance of Node.js.
Description
Version
v14.19.0
Platform
Linux 5.13.0-28-generic #31~20.04.1-Ubuntu SMP Wed Jan 19 14:08:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
libuv
What steps will reproduce the bug?
I have taken a flamegraph (https://www.brendangregg.com/flamegraphs.html) of my server code running under full load. Not sure if i could provide an example that triggers the same behaviour.
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
node v12.18.3
What do you see instead?
which is almost a 5x cpu usage increase vs the previous v14 version
Additional information
The only commit between those 2 versions that could impact libuv is this one #40631
which adds -fno-strict-aliasing
flag to libuv
Metadata
Metadata
Assignees
Labels
libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.performanceIssues and PRs related to the performance of Node.js.Issues and PRs related to the performance of Node.js.