Skip to content

dgram benchmark causes 100% CPU #1254

Closed
Closed
dgram benchmark causes 100% CPU#1254
Labels
benchmarkIssues and PRs related to Node.js benchmarks and benchmarking infrastructure.dgramIssues and PRs related to UDP and the dgram module.

Description

@mscdex
mscdex
opened on Mar 25, 2015

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?

Activity

  1. mscdex
    added
    dgramIssues and PRs related to UDP and the dgram module.
    benchmarkIssues and PRs related to Node.js benchmarks and benchmarking infrastructure.
    on Mar 25, 2015

  2. brendanashworth commented on May 10, 2015

    @brendanashworth
    brendanashworth
    on May 10, 2015
    Contributor

    This should be fixed after 18d457b.

  3. brendanashworth
    closed this as completedon May 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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