Skip to content

runtime: should NumStackOrder increase? #9045

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

Closed
rsc opened this issue Nov 2, 2014 · 0 comments
Closed

runtime: should NumStackOrder increase? #9045

rsc opened this issue Nov 2, 2014 · 0 comments
Milestone

Comments

@rsc
Copy link
Contributor

rsc commented Nov 2, 2014

NumStackOrder=3.
When it was originally chosen, the 3 cached sizes were 8k, 16k, 32k.
Now that the min stack is 2k, the 3 cached sizes are 2k, 4k, 8k.
16k and 32k are no longer cached at all.
If it made sense to cache them before, it probably still makes sense to cache them, in
which case NumStackOrder should change to 5.

Not for Go 1.4 unless we can demonstrate a real problem. So far no one seems to be
complaining.
@bradfitz bradfitz modified the milestone: Go1.5 Dec 16, 2014
@golang golang locked and limited conversation to collaborators Jun 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants