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

benchmark: disable dgram benchmark #1258

Closed
wants to merge 1 commit into from

Conversation

mscdex
Copy link
Contributor

@mscdex mscdex commented Mar 25, 2015

This is a temporary measure until dgram no longer calls callbacks
synchronously, otherwise this benchmark pegs the CPU at 100%
for an indefinite amount of time.

This is a temporary measure until dgram no longer calls callbacks
synchronously, otherwise this benchmark pegs the CPU at 100%
for an indefinite amount of time.
@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
@yosuke-furukawa
Copy link
Member

As you know, I try fixing this issue. but I have not finished. #486

I would like to fix this issue to change the following line from process.nextTick to setImmediate. https://github.com/iojs/io.js/blob/v1.x/lib/dgram.js#L325

Do you have any thoughts? @bnoordhuis
If my thought is ok, i will send a pull request with tests.

@brendanashworth
Copy link
Contributor

LGTM

@yosuke-furukawa
Copy link
Member

ref: #1313

@brendanashworth
Copy link
Contributor

Fixed since 18d457b, closing.

@mscdex mscdex deleted the disable-dgram-benchmark branch December 17, 2015 18:23
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

Successfully merging this pull request may close these issues.

4 participants