1 |
From Bron, February 28, 2019 |
From Bron Nelson, February 28, 2019 |
2 |
|
|
3 |
In the newest version, it is no longer necessary to hand-edit the |
In the newest version, it is no longer necessary to hand-edit the |
4 |
constants in "recvTask.c" and "readtile_mpiio.c". Instead, the file |
constants in "recvTask.c" and "readtile_mpiio.c". Instead, the file |
22 |
allocated to the I/O. Note that the 20 (or whatever) number is |
allocated to the I/O. Note that the 20 (or whatever) number is |
23 |
*aggregate* across all the I/O nodes, NOT a "per node" number. |
*aggregate* across all the I/O nodes, NOT a "per node" number. |
24 |
|
|
25 |
|
Another important constraint is that the total memory on all the I/O |
26 |
|
nodes *collectively* needs to be twice as big as the largest epoch you |
27 |
|
write. So, if you are writing a 1.5 TB pickup dump, then you should |
28 |
|
have a sum total of 3TB of memory (or more) on the set of I/O nodes. |
29 |
|
|
30 |
Choose dumpFreq and pChkptFreq as usual. We're not set up |
Choose dumpFreq and pChkptFreq as usual. We're not set up |
31 |
to do the rolling checkpoints yet. It'll dump u,v,t, and etan now - |
to do the rolling checkpoints yet. It'll dump u,v,t, and etan now - |
32 |
send me a list of other fields you want, as it is rather involved |
send me a list of other fields you want, as it is rather involved |