Different speed of execution of the same code in different versions Matlab. 2014b and 2017a

11 visualizzazioni (ultimi 30 giorni)
Hello. The question is this. Why are the same code executed at different speeds in different versions of matlab? Versions 2014b and 2017a.
Below are screenshots with the difference in code execution in different versions.
I noticed one strange thing. If I write code without declaring a function, then the difference in execution between versions is huge.
If the code is described as a function, then speed is greatly increased
code without declaring a function:
clear
b = rand(1000000,10);
i=1;
tic
while i <= 1000
res = b(:,1).*b(:,10);
i = i+1;
end
toc
result Matlab 2014b :
Elapsed time is 1.962136 seconds.
result Matlab 2017a :
Elapsed time is 8.741258 seconds.
code with function:
function f=Untitled
clear
b = rand(1000000,10);
i=1;
tic
while i <= 1000
res = b(:,1).*b(:,10);
i = i+1;
end
toc
end
result Matlab 2014b :
Elapsed time is 1.757147 seconds.
result Matlab 2017a :
Elapsed time is 1.885382 seconds.
p.s. Untitled is the name of the script / function
  6 Commenti
Stephen23
Stephen23 il 4 Giu 2018
"A script has access to the base workspace"
Only for scripts run from the command line (and a few other cases). The documentation states that "When you call a script from a function, the script uses the function workspace", which is not the base workspace.
Rik
Rik il 4 Giu 2018
@Stephen, I was already corrected by Walter. I misspoke because I only use scripts in the base workspace for debugging, so for all my use cases it is in fact the base workspace. But, yes, you are correct, it's not actually the base workspace necessarily, but the workspace of the calling function.

Accedi per commentare.

Risposta accettata

Philip Borghesani
Philip Borghesani il 4 Giu 2018
This feels like a bug to me and I filed a bug report. Walter is correct that coding this as a function is expected to produce faster code but there is no reason for this big a performance difference.
If you can't easily convert your code to a function I suggest posting more information about the problem you are trying to solve with actual code, or creating a support call for the best solutions to this performance issue.
  4 Commenti
Troy Norton
Troy Norton il 16 Giu 2022
Hi @Philip Borghesani, has there been any resolution to this issue? I am experiencing very similar performance degradation in some fairly simple scripts when using newer versions of Matlab. I have seen this on multiple workstations with varying specs. In general, 2014b ran nearly 10x faster than 2017b and 2019b. Look forward to your response.

Accedi per commentare.

Più risposte (1)

Walter Roberson
Walter Roberson il 3 Giu 2018
The Just In Time engine historically compiled functions more than it compiled scripts. This had to do with the fact that scripts were more free to "poof" variables into existence, so decisions involving variables that might be set in a script call had to be made at run time, whereas static analysis for functions could be more thorough.
In R2015b a new Execution Engine started making more assumptions about what was happening in scripts, and started declaring that some potential changes in scripts would no longer be paid attention to or would now be errors. As a result, performance of code that included scripts improved.
  2 Commenti
Jan
Jan il 4 Giu 2018
performance of code that included scripts improved
But not in the case mentioned by the OP:
2014b: 1.962136 seconds.
2017a: 8.741258 seconds.
Walter Roberson
Walter Roberson il 4 Giu 2018
Ah, yes, I am able to replicate the script slowdown for that code between R2014a and R2018a.

Accedi per commentare.

Categorie

Scopri di più su MATLAB Report Generator in Help Center e File Exchange

Prodotti


Release

R2017a

Community Treasure Hunt

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

Start Hunting!

Translated by