...
- With casa-6, the resulting image is dependant on the cpuset used.
https://docs.google.com/spreadsheets/d/1aKCzeCOj1-50mC7I4fN2eMupPrfR6OH-6LN4jSK9LtQ/edit#gid=2101591390
https://docs.google.com/spreadsheets/d/1aKCzeCOj1-50mC7I4fN2eMupPrfR6OH-6LN4jSK9LtQ/edit#gid=93665106
- When using 8cores and mpicasa -n 9, I casa-6 always produces the
same image regardless of the cpuset.
https://docs.google.com/spreadsheets/d/1aKCzeCOj1-50mC7I4fN2eMupPrfR6OH-6LN4jSK9LtQ/edit#gid=1339676938
- jobs jr-batch.9 and jr-nmpost005b.2 show that -n 9 is the same as
-n $machinefile when ppn is 9
- runnnig a manual job with access to all the cores (no cpuset) and -n
- 9 produces the same result as jr-nmpost005.55 (all 8 even cores).
Though I only have a few data points.
- nmpost005, nmpost006, and nmpost072 produce the same images given
the same input and using the same cpuset.
- cores chosen by Torque don't seem to change for a given host.
Though I only have a few data points. If it did vary once in a
while it could explain the once in a while differences I saw in my
end-to-end runs.
https://docs.google.com/spreadsheets/d/1aKCzeCOj1-50mC7I4fN2eMupPrfR6OH-6LN4jSK9LtQ/edit#gid=1234076945
- It seems that the specific cores chosen doesn't dictate the image
created but the number of cores on each socket does.
- It is looking like hardware doesn't really matter. It's the cpuset.
Questions
? Does the number of threads per process (ps -T <pid>) change with
different cpusets?