Matrix multiplication result - where does it go?

I've been curious, after various recent observations, about whether matrix multiplication always allocates fresh memory for its output. For example, suppose I do something like
A(:,1)=B*x;
Is this equivalent to
z=B*x; %memory allocated here
A(:,1)=z;
Or, does the output of B*x get directly generated in the memory locations occupied by A(:,1)? Obviously, the latter would be more efficient, but I wasn't sure how it worked. I know for example that this
A(1,:)=B(1,:)*x;
is equivalent to
z=B(1,:); %memory allocated here
A(1,:)=z*x;
so obviously not everything is as well optimized as it could be.

1 comentario

Cedric
Cedric el 24 de En. de 2013
Editada: Cedric el 24 de En. de 2013
I used Process Lasso to set a watchdog on MATLAB memory usage at 2GB.
In the following, n=1.36e4 is the size needed for building a matrix that will put MATLAB virt. mem usage right below 2GB on my system.
This is OK (usage ~1.8GB):
>> clear all ; n = 1.36e4 ; v = ones(n,1) ; A = zeros(n) ;
This is also OK (usage ~1.8GB):
>> clear all ; n = 1.36e4 ; v = ones(n,1) ; A = v * v.' ;
This is killed:
>> clear all ; n = 1.36e4 ; v = ones(n,1) ; A = zeros(n) ; A = v * v.' ;
I could perform more tests that fit better your initial question, but I wanted to start with something that would generate a brutal increase in memory usage if temp. memory was allocated.. which seems to be the case!
(PS: but not before tomorrow, because tonight I have to perform computations using a.. an Excel spreadsheet! ;-/)

Iniciar sesión para comentar.

 Respuesta aceptada

James Tursa
James Tursa el 24 de En. de 2013
Editada: James Tursa el 24 de En. de 2013

2 votos

Interesting question. The answer will probably depend on MATLAB version and JIT settings. TMW likely keeps stuffing more & more optimization like this into their JIT code with each version release. (E.g., the in-place operations that can sometimes take place for certain function call syntaxes.) Probably the only way to get any insight into it would be to do some timing and/or memory tests using very large arrays.
(That reminds me ... I need to finish testing & upload the new version of MTIMESX which allows in-place operations)

1 comentario

I guess that's the thing to do. Well, the following experiment seems to confirm that temporary variables are created (in 2012a), the first time measurement being pretty close to the sum of the 3rd and 4th measurements.
M=1e6; N=1;
B=rand(M,N);
x=rand(N,9);
A=rand(M,10);
tic;
A(:,1:9)=B*x;
toc;
Elapsed time is 0.043764 seconds.
tic
z=B*x; %memory allocated here
toc;
Elapsed time is 0.030972 seconds.
tic
A(:,1:9)=z;
toc
Elapsed time is 0.014324 seconds.

Iniciar sesión para comentar.

Más respuestas (0)

Categorías

Más información sobre Performance and Memory en Centro de ayuda y File Exchange.

Preguntada:

el 23 de En. de 2013

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by