At some point you will need to — or just want to — push the limits of Mathematica and it may be helpful to measure memory consumed during a computation. Here are methods inspired by Wagon, Mathematica in Action (2nd ed., pp 431 et seq.). (See also Memory Management Tools.)
The first method is simple; store the initial MemoryInUse in a variable, do your calc, then subtract it from the current MemoryInUse.
currentMemory=MemoryInUse[];
{(MemoryInUse[]-currentMemory),Plus@@(1./Range@1000000)}
{1368,14.3927}
Second, suppose you want to monitor memory in several places in your code. Initialize the variable currentMemory, then sprinkle
Sow[-currentMemory+(currentMemory=MemoryInUse[])]
through your code like Print statements, and the enclosing Reap will cause each one to output the net memory consumed in bytes between the previous use and the current one. I say 'net' memory consumed because Mathematica is designed to optimize memory use and so clears memory in use every chance it gets. Following the pattern of Timing, I reverse the output to give the memory results first, then the function's output.
currentMemory=MemoryInUse[];
(*initialize s*); s=0;
Reap[Do[If[i<25,Sow[-currentMemory+(currentMemory=MemoryInUse[])]];s+=1./i,{i,1000}];s]//Reverse
{{{3016,11216,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0}},7.48547}
Did you notice, as Wagon points out, that Do uses minimal memory during a calculation? It cleans up after every iteration.
Like Timing, this third method of checkMemory requires you to wrap your computation in checkMemory, access the result of your computation with First and if desired suppress the output with a semi-colon. Mimicking the structure of a built-in function is an example of a good programming technique. The designers of Mathematica are master programmers and they have created and debugged templates or paradigms of function structures. Often you can follow the structure of built-in functions to create sound ones of your own.
Clear@checkMemory;
checkMemory@computation_:=
Module[{computation1,preComputationMemory},
preComputationMemory=MemoryInUse[];Print["Memory in use at start is ",preComputationMemory];
computation1=computation;
memoryUsedInComputation=MemoryInUse[]-preComputationMemory;
Print["Memory in use at end is ",MemoryInUse[]];{memoryUsedInComputation,computation1}
]
Once it's done, this computation uses 32 bytes of memory and the result is 14.3927.
checkMemory[Sum[1./i,{i,1000000}]]
Memory in use at start is 31286024
Memory in use at end is 31286056
{32,14.3927}
We find the memory use with the function output for a small Table.
s1=0;checkMemory[Table[s1+=1./i,{i,10}]]
Memory in use at start is 31289472
Memory in use at end is 31289752
{280,{1.,1.5,1.83333,2.08333,2.28333,2.45,2.59286,2.71786,2.82897,2.92897}}
Then suppress output, with a semi-colon as is done in Timing, for a large Table.
checkMemory[s1=Table[1./i,{i,10^7}];]
Memory in use at start is 31340688
Memory in use at end is 111344696
{80003992,Null}
I left off the summation of the Table to show MemoryInUse during the calc. If we add Total, we see the max MemoryInUse reclaimed (-80,000,024 bytes).
Timing[checkMemory[s1=Table[1./i,{i,10^7}]//Total]]
Memory in use at start is 31359736
Memory in use at end is 31359864
{0.343202,{128,16.6953}}
Compare memory used in a Do loop. Pretty interesting!
Timing[s1=0;checkMemory[Do[s1+=1./i,{i,10^7}];s1]]
Memory in use at start is 31364400
Memory in use at end is 31364432
{10.296066,{32,16.6953}}
First@%/First@%%
30.0000
So there you have it, Do takes 30 times as long as the functional command Table[...]//Total, but uses a minute fraction of the latter's memory.
The first method is simple; store the initial MemoryInUse in a variable, do your calc, then subtract it from the current MemoryInUse.
currentMemory=MemoryInUse[];
{(MemoryInUse[]-currentMemory),Plus@@(1./Range@1000000)}
{1368,14.3927}
Second, suppose you want to monitor memory in several places in your code. Initialize the variable currentMemory, then sprinkle
Sow[-currentMemory+(currentMemory=MemoryInUse[])]
through your code like Print statements, and the enclosing Reap will cause each one to output the net memory consumed in bytes between the previous use and the current one. I say 'net' memory consumed because Mathematica is designed to optimize memory use and so clears memory in use every chance it gets. Following the pattern of Timing, I reverse the output to give the memory results first, then the function's output.
currentMemory=MemoryInUse[];
(*initialize s*); s=0;
Reap[Do[If[i<25,Sow[-currentMemory+(currentMemory=MemoryInUse[])]];s+=1./i,{i,1000}];s]//Reverse
{{{3016,11216,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0}},7.48547}
Did you notice, as Wagon points out, that Do uses minimal memory during a calculation? It cleans up after every iteration.
Like Timing, this third method of checkMemory requires you to wrap your computation in checkMemory, access the result of your computation with First and if desired suppress the output with a semi-colon. Mimicking the structure of a built-in function is an example of a good programming technique. The designers of Mathematica are master programmers and they have created and debugged templates or paradigms of function structures. Often you can follow the structure of built-in functions to create sound ones of your own.
Clear@checkMemory;
checkMemory@computation_:=
Module[{computation1,preComputationMemory},
preComputationMemory=MemoryInUse[];Print["Memory in use at start is ",preComputationMemory];
computation1=computation;
memoryUsedInComputation=MemoryInUse[]-preComputationMemory;
Print["Memory in use at end is ",MemoryInUse[]];{memoryUsedInComputation,computation1}
]
Once it's done, this computation uses 32 bytes of memory and the result is 14.3927.
checkMemory[Sum[1./i,{i,1000000}]]
Memory in use at start is 31286024
Memory in use at end is 31286056
{32,14.3927}
We find the memory use with the function output for a small Table.
s1=0;checkMemory[Table[s1+=1./i,{i,10}]]
Memory in use at start is 31289472
Memory in use at end is 31289752
{280,{1.,1.5,1.83333,2.08333,2.28333,2.45,2.59286,2.71786,2.82897,2.92897}}
Then suppress output, with a semi-colon as is done in Timing, for a large Table.
checkMemory[s1=Table[1./i,{i,10^7}];]
Memory in use at start is 31340688
Memory in use at end is 111344696
{80003992,Null}
I left off the summation of the Table to show MemoryInUse during the calc. If we add Total, we see the max MemoryInUse reclaimed (-80,000,024 bytes).
Timing[checkMemory[s1=Table[1./i,{i,10^7}]//Total]]
Memory in use at start is 31359736
Memory in use at end is 31359864
{0.343202,{128,16.6953}}
Compare memory used in a Do loop. Pretty interesting!
Timing[s1=0;checkMemory[Do[s1+=1./i,{i,10^7}];s1]]
Memory in use at start is 31364400
Memory in use at end is 31364432
{10.296066,{32,16.6953}}
First@%/First@%%
30.0000
So there you have it, Do takes 30 times as long as the functional command Table[...]//Total, but uses a minute fraction of the latter's memory.
