...
- 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
- Torque seems to choose different cpusets for different hosts. E.g. nmpost005 gets 0-1,3-5,7,9,11,13 while nmpost006 gets 0-2,4-6,8,10,12. This cpuset doesn't seem to change after a reboot nor after smaller jobs being run on the host. I have no idea where Torque is saving this cpuset between jobs but it seems to be doing just that. This could produce different images if you are using something like ppn:8 and -n 8 or -n machinefile and you may think it is host dependent when actually it may just be Torque choosing different cpusets for you.
- It seems that the specific cores chosen doesn't dictate the image created but the number of cores on each socket does.
...