Skip to content

deprecate shows increased use of CPU #58218

Open
@slagiewka

Description

@slagiewka

Version

v24.0.0

Platform

Happening in many environments I've tested:
Docker: `Linux 1633ae2ed477 6.10.14-linuxkit #1 SMP Thu Mar 20 16:32:56 UTC 2025 aarch64 GNU/Linux`
Native macOS: `Darwin host.local 24.3.0 Darwin Kernel Version 24.3.0: Thu Jan  2 20:24:16 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6000 arm64`

Subsystem

No response

What steps will reproduce the bug?

A simple code with standard library only. Added some limiting to keep it running while inspecting. It might not be balanced for best performance and showing the major perf hit.

node --inspect index.js
for (let index = 0; index < 20_000; index++) {
  const proms = [];
  for (let index = 0; index < 100; index++) {
    proms.push(
      fetch("https://nodejs.org", {
        signal: AbortSignal.timeout(1000),
      })
        .then((res) => res.text())
        .then(console.log)
        .catch(console.log),
    );
  }

  await Promise.all(proms);
}

How often does it reproduce? Is there a required condition?

100% on node v24.

What is the expected behavior? Why is that the expected behavior?

No time spent on deprecate shows in performance tools.

What do you see instead?

Significant time spent on deprecate (real project shows higher use than the example).

Image

Additional information

FWIW there are no deprecation warnings issued to the console output.

I do not see this behaviour in v23.

Metadata

Metadata

Assignees

No one assigned

    Labels

    performanceIssues and PRs related to the performance of Node.js.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions