Why tic/toc reports slower times the first five iterations?
4 vues (au cours des 30 derniers jours)
Afficher commentaires plus anciens
for i = 1:10
tic
a=2*3;
toc
end
0 commentaires
Réponses (2)
Bruno Luong
le 13 Sep 2022
Modifié(e) : Bruno Luong
le 13 Sep 2022
If I remember, the JIT optimizer decides to kick in when the same code is detected by execution engine to run few times (5).
1 commentaire
Walter Roberson
le 13 Sep 2022
Historically, during the time period that Mathworks used the phrase JIT, then a limited set of operations were supported, and the optimization did not kick in the first pass.
However now that they use the term "execution engine", supposedly all execution goes through it, and supposedly it starts immediately, with the analysis at the time the code is parsed. Supposedly.
That said, in a fair number of tests, I have seen the second and third iterations take much of time.
Image Analyst
le 13 Sep 2022
There is some randomness to it. Your computer does other things you know. Who knows what else it may have been doing while that code was running? When I run it I get different numbers every time, though the the first one is always the longest and they are much shorter than yours.
Elapsed time is 0.000002 seconds.
Elapsed time is 0.000002 seconds.
Elapsed time is 0.000001 seconds.
Elapsed time is 0.000000 seconds.
Elapsed time is 0.000000 seconds.
Elapsed time is 0.000000 seconds.
Elapsed time is 0.000000 seconds.
Elapsed time is 0.000000 seconds.
Elapsed time is 0.000000 seconds.
Elapsed time is 0.000000 seconds.
0 commentaires
Voir également
Catégories
En savoir plus sur Logical dans Help Center et File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!