laggy issue of code editor in R2018b
24 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
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 Kommentare
Antworten (4)
Kris Fedorenko
am 3 Okt. 2018
Bearbeitet: Kris Fedorenko
am 3 Okt. 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 Kommentare
Josh Carlile
am 19 Jan. 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
am 23 Apr. 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
am 27 Jun. 2019
I encoutered the same problem on both r2018b and r2019a. The solution is to turn off Magnet.
Hope it helps.
0 Kommentare
Daniel Pantea
am 22 Okt. 2018
Bearbeitet: Daniel Pantea
am 22 Okt. 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 Kommentare
Daniel Pantea
am 25 Okt. 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;
Siehe auch
Kategorien
Mehr zu Loops and Conditional Statements finden Sie in Help Center und File Exchange
Produkte
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!