-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Huge input lag when browsing through code on RPi B+ v1.2 in console mode [Nano is much faster] #2970
Comments
2.0.8 is one of the old ones too. :) There is definitely a room for optimization in micro, but such a huge slowdown is suspicious. I was going to suggest to run micro with |
Oh, that might be worth testing. I honestly just installed running I will update to the latest version and report back my results (in 2 years, maybe, after gcc 13.2 finishes compiling in my veteran B+ 1.2 ¬¬) #okno Cheers |
Hi @dmaluka Unfortunately, upgrading my version to the latest did not solve the issue. I had to manually compile from source (which was particularly cumbersome as I had to install Go-taking several hours) Any other ideas to increase performance? |
I wasn't really hoping that updating to the latest version will improve performance, but the latest version has BTW is the CPU consumption by micro very high when the lag is observed? If it's not, then maybe this profiling will not tell much, since it's rather micro waiting on some external events for too long, than consuming too many CPU cycles. |
I experience very similar behavior on my pi zero - nano works fine but micro has high input lag. Versions:
|
Thanks for sharing the profile. Looks like the two biggest CPU hoggers in micro on your RPi are the same as what I see on my i7-7600U. I've created issues for both: Although they are not causing an actual slowdown for me (they are just causing higher CPU usage than e.g. in vim or nano, but still way below 100%), which is no wonder, due to a much more performant CPU than the BCM2835 on your RPi. (Although even if I throttle the CPU frequency down to 400 MHz I still see no lag, except some lag when quickly selecting text via mouse. But again, probably no wonder, since I still have much bigger CPU cache and so on.) That said, I'm still not entirely sure if that is the actual cause of the lag you are seeing. So for now I just have a couple of questions:
|
The input lag occurs without scrolling. If I hold the right arrow down for about 5 seconds, the cursor will keep moving for an additional 5 seconds after letting go. Holding for 10 seconds gives me an additional 10 seconds after letting go. Reading in |
Thanks, this is a really useful info. If it's not too difficult, you can try to compile micro with a change I mentioned in #3227 (comment) and see if it improves anything. (I suppose it's easy: |
Also a quick question just in case: if micro is running but you don't do anything in it, then |
Yep, no cpu usage from micro when I'm just idling. |
I've added two comparable |
Description of the problem or steps to reproduce
Input lag with keyboard (compared to Nano 5.4) is atrocious (nearly unusable). Simply pressing the arrow keys to navigate through the code is a painful experience with micro (which I deeply love 😢).
Specifications
Using micro 2.0.8 on a recently dusted Raspberry Pi B+ v1.2 (yes, one of the old ones) in console mode ONLY (no desktop to save resources).
Tested with the codebase from the picalc-chudnovsky repo.
Nano editor lag:
Nano-Lag.mp4
Micro editor lag (lifting my figers to show the lag after pressing arrow-down):
Micro-Lag.mp4
Commit hash: 2.0.8
OS: Raspbian 11
(Linux 6.1.21+)
Terminal: Native
The text was updated successfully, but these errors were encountered: