Why the new version of matlab/simulink 2016b is too slow ?

I was running a code using Matlab/Simulink 2016a without any problem. Because the university updated to 2016b version, now the SAME CODE is taking ages. ( With 2016a version it used to take about 20 minutes to finish, now it takes more than 2 hours). Something additional is that I am using the network of the university and from one day, when the university updated the software, to the next started this issue. Can you image waiting more than two hours to get some result. Please somebody could help me because here in the university does not give me any solution.

Answer 1

[John D'Errico]

In general, I saw no significant increase or decrease in speed when I moved to R2016b. Certainly not an order of magnitude change.

There are surely multiple reasons why it MIGHT be a problem. We don't see your code though. We don't have access to your search path or your computer.

For example, I might wonder if the new version is set to run off a network, whereas the older release was running locally. That will cause larger access times for functions.

Sorry, but this is not a question that we can really answer. Anything would be a wild guess. You need to talk to your MATLAB administrator.

Answer 2

[Ignacio Ortiz de Landazuri]

I have the same problem. The same code with Matlab R2013b takes 45 seconds, but with MAtlab R2017a takes 845 seconds. I was making probes with diferent version of Matlab and I realized that newer version are slower than older. That's make any senses?

[Adam]

It depends entirely on what your specific code is. Certainly Matlab R2017a is not globally 20 times slower than Matlab R2013b