Why Matlab 2017a needs twice more time than 2014a to run the same code?
2 views (last 30 days)
Show older comments
A. Wozniak
on 16 Mar 2018
Commented: Julien Volle
on 19 Jul 2019
Dear all,
I have a code, which in 2014a took 16 hours to run. There is a lot of parfor loops, which works smoothly. The same code, with identical data needed 30 hours to run.
Could anyone please explain me why? What can I do, to work it faster? I heard, that 2017 versions are supposed to be faster... So, what's wrong?
Thank you in advance for any clues.
4 Comments
Accepted Answer
Fangjun Jiang
on 16 Mar 2018
I would suggest you contacting Mathworks' technical support for this. If you could provide your example data, I am sure they will be able to find out why and possibly provide a solution. I had a similar issue where it took much longer in R2015b to finish a script than in R2014b. It turned out that there is some optimization in MATLAB R2015b that inadvertently slows down a particular use case. The tech support found the root cause and the problem was resolved in R2016b.
3 Comments
Julien Volle
on 19 Jul 2019
No, never. They adised me to switch to the newest version of Matlab. And indeed, I didn't have this problem in the newer version.
More Answers (0)
See Also
Categories
Find more on Loops and Conditional Statements in Help Center and File Exchange
Products
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!