| 54 | | I've run a pantasks using only the stare nodes, with 8x loading (40 active jobs, based in /data/ippc19.0/home/watersc1/itc_sync_script.20161026/test_pant). This seemed to have no impact on the cluster, although no nightly science observations were taken. I've also updated the ipptest/replication directory to match this, and supplied it with the split file lists of commands. Based on the ipplanl/stdlocal pantasks input, I've copied (but commented out) turn.on/off.storage tasks into this input, but I'm not sure what the correct loading should be (which is why these are commented out). |
| | 54 | I've run a pantasks using only the stare nodes, with 8x loading, plus additional x node power (x2, x3 using 6x loading, x1 using 2x) (~300 active jobs, based in /data/ippc19.0/home/watersc1/itc_sync_script.20161026/test_pant). This seemed to have no impact on the cluster, although no nightly science observations were taken. I've also updated the ipptest/replication directory to match this, and supplied it with the split file lists of commands. Based on the ipplanl/stdlocal pantasks input, I've copied (but commented out) turn.on/off.storage tasks into this input, but I'm not sure what the correct loading should be (which is why these are commented out). This runs as the ipptest user, simply to have a group user managing the process. |
