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

Set GOMAXPROCS for etcd #7863

Merged
merged 1 commit into from
May 7, 2015
Merged

Conversation

fgrzadkowski
Copy link
Contributor

@@ -1,3 +1,5 @@
{% set num_nodes = salt['grains.get']('num_cpus', '') %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

num_cpus as a name maybe?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops :) I copy&pasted this line from an example and forgot to change the variable name. Thanks!

@wojtek-t
Copy link
Member

wojtek-t commented May 7, 2015

LGTM

@wojtek-t wojtek-t added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 7, 2015
wojtek-t added a commit that referenced this pull request May 7, 2015
@wojtek-t wojtek-t merged commit 600b00f into kubernetes:master May 7, 2015
@timothysc
Copy link
Member

kind of sledgehammering it, ideally it would be good to know optimal values.

@lavalamp
Copy link
Member

lavalamp commented May 7, 2015

@timothysc optimal value probably depends on the number of cores & workload; this seems like a good guess. When I've tried optimizing GOMAXPROCS for other go programs, number of cpus+1 seemed the best. But etcd could be very different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Slow etcd
5 participants