Changes between Version 8 and Version 9 of u/erica/memoryBaseline

Timestamp:

02/05/14 13:41:17 (11 years ago)

Author:

Erica Kaminski

Comment:

—

u/erica/memoryBaseline

@@ -17 +17 @@
 2. Astrobear on disk (ls -lh astrobear) is 7 mb on bluehive, 6 on bamboo.
 3. This baseline memory > 20*astrobear on disk. Meaning, in addition to holding the executable in memory on each processor, there is an additional ~180mb being loaded on each processor. This could be due to shared libraries, mpi, etc.?? 
-4. Then in addition to total memory being used for info allocations (in astrobear.log), one should also add this "baseline" memory when trying to estimate the total memory the simulation is using. For example, if my baseline is 0.2 GB/processor, than the baseline = 1.6 GB per node with 8 processors. Now we can use that when trying to understand the total memory being used, as reported in bluehive.log at the end of a simulation, as the following tables shows.
+4. Then in addition to total memory being used for info allocations (in astrobear.log), one should also add this "baseline" memory when trying to estimate the total memory the simulation is using. For example, if my baseline is 0.2 GB/processor, than the baseline = 1.6 GB per node with 8 processors. Now we can use that when trying to understand the total memory being used, as reported in bluehive.log at the end of a simulation, as the following tables show.
 
-For total info allocations being reported as ~ 200 mb (~.2 GB), 1 node/8 processors, bluehive.log reports :
+For total info allocations being reported as ~ 200 mb (~.2 GB), on 1 node/8 processors, bluehive.log reports :
 || Resource || Requested || Used    ||
 || memory (GB)|| 16.0    || 2.0     ||