-
Notifications
You must be signed in to change notification settings - Fork 21
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
Profiling infrastructure #136
Conversation
Here's an example of a CHANGELOG.md entry: * [#136](https://github.com/PCMSolver/pcmsolver/pull/136): Profiling infrastructure - [@robertodr](https://github.com/robertodr) Generated by 🚫 Danger |
Codecov Report
@@ Coverage Diff @@
## release/1.2.Z #136 +/- ##
==============================================
Coverage 69.81% 69.81%
==============================================
Files 92 92
Lines 5625 5625
==============================================
Hits 3927 3927
Misses 1698 1698 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very good. I started using perf after you have recommended and it is indeed a nice tool. The doc here is great.
Thanks! I'll rebase and then you can push the button. |
This PR provides documentation and infrastructure for profiling the library. Of the tools I have explored, only
gperftools
needed some CMake infrastructure. I haven't consideredgprof
: according to the Internet it's basically deprecated in favor ofperf
.The set of input files for benchmarking should definitely be expanded to stress-test different parts of the code.
Todos
perf
.Types of changes
Status