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

Jump to bottom

crypto/tls: mention cpu frequency scaling in "why does using GOMAXPROCS > 1 sometimes make my program slower?" #7791

Closed
gopherbot opened this issue Apr 15, 2014 · 1 comment
Closed

crypto/tls: mention cpu frequency scaling in "why does using GOMAXPROCS > 1 sometimes make my program slower?" #7791

gopherbot opened this issue Apr 15, 2014 · 1 comment
Labels
FrozenDueToAge

Comments

@gopherbot
Copy link

by giantchen:

When I was benchmarking TLS handshaking with http://play.golang.org/p/WZlt7mI4WN , I
noticed that using GOMAXPROCS > 1 does make my program significantly slower (1.5x ~
2x). And I found the reason to be CPU frequency scaling, because no threads run hot
enough to stimulate CPU cores.

May be worth mention that in the FAQ.
@bradfitz
Copy link
Contributor

Comment 1:

Frequency scaling (if it was your problem) would also affect the GOMAXPROCS == 1 case,
so it doesn't seem worth mentioning there in the FAQ.  It's also possibly misleading.

Status changed to WontFix.

@mikioh mikioh changed the title faq: mention cpu frequency scaling in "why does using GOMAXPROCS > 1 sometimes make my program slower?" crypto/tls: mention cpu frequency scaling in "why does using GOMAXPROCS > 1 sometimes make my program slower?" Jan 15, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bradfitz @gopherbot