-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Addition of the CPU ID info #39982
Comments
A new Issue was created by @silviodonato Silvio Donato. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign core |
New categories assigned: core @Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks |
The framework job report should contain the CPU model if the As part of #30044 we are going to store the CPU model (among other information) in the data files such that it can be obtained programmatically, but this development will still take quite some time. In the mean time, if the job report and any other computing-side monitoring are not sufficient, a quick&dirty way would be to store the CPU model string e.g. as a data product in LuminosityBlock. |
Thank you Matti, I'm closing this ticket as it is a kind of duplicate of #30044 |
Dear @cms-sw/core-l2 ,
do we have somewhere the information about which CPU has been used to run CMSSW?
In https://its.cern.ch/jira/browse/CMSHLT-2257 we realized that there are sizable differences between Intel and AMD (at least at the HLT), related to the -Ofast flag.
In https://its.cern.ch/jira/browse/PDMVRELVALS-159 we are planning to run an offline validation AMD vs Intel, but it seems difficult to submit jobs selecting the CPU family. So we are going to submit the jobs on T2_CH_CERN (which is made of mainly AMD) and T2_CH_CERN_HLT which is only Intel.
Therefore, I'd like to know if there is a possibility to know if an event has been processed by Intel or AMD.
Thank you,
Silvio.
The text was updated successfully, but these errors were encountered: