Skip to content

dgram benchmark causes 100% CPU #1254

Description

@mscdex

This is related to #486 from earlier this year.

The problem still exists though and is kind of annoying when you're wanting to execute all benchmarks. Can we at least temporarily disable the dgram benchmark entirely until it gets fixed?

Metadata

Metadata

Assignees

No one assigned

    Labels

    benchmarkIssues and PRs related to Node.js benchmarks and benchmarking infrastructure.dgramIssues and PRs related to UDP and the dgram module.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions