Create SPEC CPU pinning to NUMA

[v-safilho]

SPEC CPU pinning binds benchmark processes to specific CPU cores/NUMA nodes, reducing scheduling and memory-placement variability. This enables more consistent performance results and controlled comparisons across CPU/NUMA topology

#pbi 39982524

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[alexffrank]

Samuel, please add a property into Metricds.CustomDimensions.metadata_scenario reflecting the status of NUMA/Core pinning. No info is ok (and backwards compatible) to imply there is no affinity/pinning.

[alexffrank]

Samuel, per SPEC CPU documentation NUMA/Core affinity is controlled via a configuration file of the workload.
https://open.spec.org/cpu2017/Docs/config.html

I'm yet to find whether this change follows the SPEC CPU spec. Does it?
(if yes, could you please point to the relevant source code?)

IDK whether SPEC CPU 2026 is backwards compatible to 2017's configuration. If not, I would submit two distinct PRs.

[v-safilho]

Samuel, please add a property into Metricds.CustomDimensions.metadata_scenario reflecting the status of NUMA/Core pinning. No info is ok (and backwards compatible) to imply there is no affinity/pinning.

implemented here

[v-safilho]

Samuel, per SPEC CPU documentation NUMA/Core affinity is controlled via a configuration file of the workload. https://open.spec.org/cpu2017/Docs/config.html

I'm yet to find whether this change follows the SPEC CPU spec. Does it? (if yes, could you please point to the relevant source code?)

solution implemented here, follows the SPEC CPU spec configuration. I am injecting numactl into the generated SPEC .cfg, so SPEC invokes numactl separately.

SPEC CPU allows a submit command to bind benchmark processes:
numactl --physcpubind for CPU/core affinity plus -l or -m for NUMA-aware memory placement on multi-socket/NUMA systems.

SPEC CPU2017 Platform Settings for HPE ProLiant Intel-based systems

[v-safilho]

Ubuntu 26.04.1 LTS Evidences collected from Juno Orchestrator

[v-safilho]

Ubuntu 24.04.4 LTS Evidences collected from Juno Orchestrator

[v-safilho]

updated to accomplish the new VirtualClient naming convention CopyCount and ThreadCount.
ex.: --parameters="CopyCount=4,,,ProcessorAffinity=0,1,48,49"