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

Zero allocation fix #226

Merged
merged 1 commit into from
Oct 11, 2017
Merged

Conversation

sergiud
Copy link
Collaborator

@sergiud sergiud commented Aug 8, 2017

This is an alternative to PR #217 which does not allocate dynamic memory.

@sergiud
Copy link
Collaborator Author

sergiud commented Oct 10, 2017

@shinh The PR is ready to be merged!

@shinh
Copy link
Collaborator

shinh commented Oct 11, 2017

Looks great, thanks! I'm fairly sure LOG(INFO) is still allocation free, but have you somehow checked this didn't increase memory allocation?

@shinh shinh merged commit d053142 into google:master Oct 11, 2017
@sergiud
Copy link
Collaborator Author

sergiud commented Oct 12, 2017

I have no numbers. However, @hansres has been running the patch for an extended period of time and maybe he can comment on that.

Nevertheless, since there's just one static array per thread, the memory consumpution should not bet higher than without TLS.

durswd pushed a commit to durswd/glog that referenced this pull request Sep 2, 2019
@sergiud sergiud deleted the zero-allocation-log-failure branch February 12, 2022 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants