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
Extend jmalloc to monitor the peak memory usage of each thread (11.2.x) #5852
Extend jmalloc to monitor the peak memory usage of each thread (11.2.x) #5852
Conversation
@cmsbuild, please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
jemalloc.spec
Outdated
%define branch master | ||
%define github_user jemalloc | ||
%define branch 52x-peakmem | ||
%define github_user fwyzard |
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.
If we go with the patch, we should probably fork jemalloc
under https://github.com/cms-externals/
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.
Sure - this is just a way to show what the changes would be, and make sure it doesn't break anything in CMSSW.
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
please test |
The tests are being triggered in jenkins. |
Pull request #5852 was updated. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_11_2_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
See jemalloc/jemalloc#1176 and jemalloc/jemalloc#1850 for the discussion with the jemalloc development team.