-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Memory allocation optimizations #71
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
Conversation
LGTM - very, even but I can't test before monday. |
I didn't test on Linux, but I ran the benchmarks on OS X - with the regression you mentioned. Before (master 5f91140):
After (mem-pool a2310d9):
|
For completeness, here's the results from Brads master 1624047:
|
Feel free to revert any parts which make things slower for now. But also In the future, once we have Feel free to do whatever in the meantime. On Mon, May 13, 2013 at 3:40 AM, Arne Hormann notifications@github.comwrote:
|
less tmp slices
too many changes to rebase
Based on the great work by @bradfitz in #68
I can see a small performance regression on my Windows system. But Windows is sometimes a bit uh.. strange and Go is more optimized for Linux systems.
Unfortunately I currently have no Linux system where I could properly test this.
So can you please provide benchmark results?
I'd like to see the results of this change on various systems.