Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: heap size increases from go1.8b2 to go1.9 (for map objects?) #21641
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
I'm not sure what the issue here is. Your first example runs faster by all metrics in Go 1.9 and your second example consumes less user and system time with Go 1.9, which suggests that the slightly higher real time is from system noise or frequency scaling. I'm not particularly concerned about a 0.5% increase in RSS (especially without statistically significant evidence that there actually is a change; though even then I wouldn't be particularly concerned).
Perhaps you could clarify what the concern is?
The time spent by each program varies a lot (it's reported by "time ./binary" from bash - I just did some re-run and get 2.76vs2.88, 2.82vs2.71) so I don't think it is saying Go 1.9 is consistently slower or faster in a conclusive way.
But in all my runs there is an increase in heap size in 1.9. The difference is small but consistent.
I'm fine if you say this is expected / known / too small to have real negative impact, etc.
const size = 10000000 / 10
const size = 10000000 / 100