Profiling: Enable profiling in code using google-perftools #1539
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow obtaining cpu and/or heap profile on specified parts of the code using tools from google-perftools package. The libraries are optionally linked in according to the
meson_option.txtsetting. The profilers can be switched on and off in the desired section of code using conditional compilation flags. Some basic instructions are included in the code.Profiling the whole app can be done from the commandline without compiling in the libraries but the advantage of having the libraries compiled in is that profiling can be switched on and off in specific parts of the code only.
By default the libraries are not compiled in so these changes will have no effect on the 'ordinary' user.