Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dgram benchmark causes 100% CPU #1254

Closed
mscdex opened this issue Mar 25, 2015 · 1 comment
Closed

dgram benchmark causes 100% CPU #1254

mscdex opened this issue Mar 25, 2015 · 1 comment
Labels
benchmark Issues and PRs related to the benchmark subsystem. dgram Issues and PRs related to the dgram subsystem / UDP.

Comments

@mscdex
Copy link
Contributor

mscdex commented 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?

@mscdex mscdex added dgram Issues and PRs related to the dgram subsystem / UDP. benchmark Issues and PRs related to the benchmark subsystem. labels Mar 25, 2015
@brendanashworth
Copy link
Contributor

This should be fixed after 18d457b.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmark Issues and PRs related to the benchmark subsystem. dgram Issues and PRs related to the dgram subsystem / UDP.
Projects
None yet
Development

No branches or pull requests

2 participants