laggy issue of code editor in R2018b
22 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
I am using Macbook Pro 2014. 2.6Ghz i5 processor, 8GM 1600Mhz memory. I installed two versions of matlab, 2015a and 2018b. When I edited my codes in 2015a, everything is fine. However, running 2018b on the same machine, the code editor is very laggy. By "laggy", I mean when I simply tried to move the cursor or type some texts, it may respond after 1-2 seconds. Sometimes, the left bottom corner popped out info "processing...". I didn't see this info in the previous matlab version. Is the new version running something new in the back to cause this laggy issue? Am I the only one having this problem?
3 comentarios
Josh Parks
el 1 de Oct. de 2018
I'm having the same issue with a MacBook Pro 2015. 2018a has no issues
Respuestas (4)
Kris Fedorenko
el 3 de Oct. de 2018
Editada: Kris Fedorenko
el 3 de Oct. de 2018
There were instances of similar behavior in R2018b caused by the Magnet app. Turning it off should resolve the issue. Alternatively, you should be able to use keyboard shortcuts with no delays.
8 comentarios
Josh Carlile
el 19 de En. de 2021
Quitting magnet solved the problem. Fantastic find!
I haven't seen any way to opt-out Matlab from Magnet but if anyone has suggestions please share
Jonas Hofbauer
el 23 de Abr. de 2022
When Matlab is open, you can go into the Magnet settings via the menu-bar dropdown and tick "Igonre Matlab" – resolved the issue for me!
Fan Zhang
el 27 de Jun. de 2019
I encoutered the same problem on both r2018b and r2019a. The solution is to turn off Magnet.
Hope it helps.
0 comentarios
Daniel Pantea
el 22 de Oct. de 2018
Editada: Daniel Pantea
el 22 de Oct. de 2018
Seems not only MAC is affected. I have same delays in Windows 7 x64. Tested same script and: - with R2018b it needed 23.4s to process the data. - with R2018a it needed 17.21s to process the same data. I have to go back to R2018a as in some situations the display gets unresponsive for seconds with R2018b! Hope they come with some patches, else this is a step back...
5 comentarios
Daniel Pantea
el 25 de Oct. de 2018
I got great help from support and they identified a place of optimization which reduced the consumed time about 10 times! Details are below and after that the elapsed time difference from 2018b vs 2018a was insignificant:
- 17a: 1.931015 seconds.
- 18a: 2.253766 seconds.
- 18b: 2.268560 seconds.
Here's detail of the improvement (which are specific to my case) I received from support:
Around line 775 in the SCRIPT.m, there is a very tight loop:
for i = 1:N1
k = min(i, mean_len);
my_mean = (my_mean*(k-1)+hUI.preprocessed{1}{ch}(i)) / k;
hUI.preprocessed{3}{ch}(i) = my_mean;
end
Using temporary variables to hoist some of the indexing out of the loop will make a huge difference:
tempVar3 = hUI.preprocessed{3}{ch};
tempVar1 = hUI.preprocessed{1}{ch};
for i = 1:N1
k = min(i, mean_len);
my_mean = (my_mean*(k-1)+tempVar1(i)) / k;
tempVar3(i) = my_mean;
end
hUI.preprocessed{3}{ch} = tempVar3;
Ver también
Categorías
Más información sobre Loops and Conditional Statements en Help Center y File Exchange.
Productos
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!