Add cpuset size information to the FJR. #15760
Conversation
We have found that it's difficult to detect when the cpuset (set by
some batch systems) is limiting the number of cores we can run on.
In one extreme case, the batch system arguments were being done
incorrectly and 32 cores worth of CMS jobs were being forced onto a
single core.
This records the current cpuset size to the FJR when CPU information
reporting is enabled. The resulting line looks like:
<Metric Name="cpusetCount" Value="1"/>
With this, we hope that experts are more likely to notice that the
cpuset is different from expectations
|
@smuzaffar Why didn't the bot see this pull request ? |
|
A new Pull Request was created by @bbockelm (Brian Bockelman) for CMSSW_8_1_X. It involves the following packages: FWCore/Services @cmsbuild, @smuzaffar, @Dr15Jones, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
|
please test |
|
+1 |
|
The tests are being triggered in jenkins. |
cmsbuild
added
core-approved
fully-signed
and removed
core-pending
pending-signatures
labels
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
|
+1 |
We have found that it's difficult to detect when the cpuset (set by
some batch systems) is limiting the number of cores we can run on.
In one extreme case, the batch system arguments were being done
incorrectly and 32 cores worth of CMS jobs were being forced onto a
single core.
This records the current cpuset size to the FJR when CPU information
reporting is enabled. The resulting line looks like:
With this, we hope that experts are more likely to notice that the
cpuset is different from expectations