I uninstalled MATLAB 2017a and installed 2016b. Now my code runs as fast as it used to. I do not know why the code suddenly started running slow in 2017a.
MATLAB 2017a was running properly, but suddenly became very slow
6 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Hello,
I am running a big code in MATLAB 2017a in windows 10 to perform some data assimilation. The code calls cygwin to run a software written in C, the result of this software is analyzed and processed. My code was running as expected but it suddenly became very slow for some reason. I uninstalled and reinstalled MATLAB which was of no use. Even the boot speed is slow. I ran the 'bench' code and got:
bench
0.1788 0.1172 0.2570 0.0989 2.2075 1.9787
System specs are i7 quad core, 16gb RAM, 2.60GHz. If anyone has an idea that could help solve the problem, please let me know. Thanks!
4 comentarios
Darío Pérez
el 9 de Ag. de 2018
Similar problem here still unresolved. Please refer to my comment in: Why my Matlab 2017a is so slow for even simple commands?
Jan
el 9 de Ag. de 2018
"Even the boot speed is slow" - this means, that it is not a Matlab problem and the question is off-topic in this forum. Maybe a problem with overheating of the CPU or a trojan which let the CPU search for bitcoins?
Respuestas (2)
Philip Borghesani
el 8 de Jun. de 2017
Completely outlandish idea. You could check if Windows enabled the fault tolerant heap for MATLAB. You can check by looking for this registry entry: Go to the HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER versions of Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers\matlab.exe and delete the FaultTolerantHeap entry. Information came from this stack overflow question.
3 comentarios
Philip Borghesani
el 8 de Jun. de 2017
That may be something else but it could still have caused the problem, no recent MATLAB should need any AppCompatFlags to work properly on Windows 10. I would go ahead and delete any keys with matlab.exe in them.
Don Zheng
el 8 de Jun. de 2017
The bench outputs look normal. You might want to profile your code and first identify which section of the code is running slow.
2 comentarios
Jan
el 9 de Ag. de 2018
You cannot compare the benchmark output between different Matlab versions, because the code of bench.m might have changed. Care for using the same function to be sure: Create a copy of bench.m and call it bench2016b.m and run it in both versions.
Ver también
Categorías
Más información sobre Startup and Shutdown en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!