I mean, the values not being constant is expected, for example in 3na-spr the two DUTs are located on different NUMA nodes of the same machine.

The bug is for some places of the CSIT code to assume they are constant and consume values set by Create Compute Resources Variables keyword.
One possible fix is to change the variable names to include which DUT they apply to.

The current code leads to "division by zero" error [0] in ipsec swasync scheduler tests, due to cpu_dp test variable last set for DUT2 is not valid for DUT1.

[0] https://s3-logs.fd.io/vex-yul-rot-jenkins-1/csit-vpp-perf-verify-master-3na-spr/3/log.html.gz#s1-s1-s1-s1-s1-t3-k2-k11-k1