Context Navigation

memoryBaseline

v12	v13
16	16	1. Baseline memory can be different on different machines, probably not by much.
17	17	2. Astrobear on disk (ls -lh astrobear) is 7 mb on bluehive, 6 on bamboo.
18		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.??
	18	3. This baseline memory > 20*astrobear on disk (although this is an upper estimate on the code -- given I was only able to collect data for compiling with hypre -- this large difference might be largely due to Hypre). 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.??
19	19	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.
20	20