-
Notifications
You must be signed in to change notification settings - Fork 24
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
Performance issues on Windows #9
Comments
@joncol try to debug that issue with profiler Probably that answer can help you http://stackoverflow.com/a/25326326 |
@joncol I'm afraid I'm not sure, there's a similar issue raised here domtronn/all-the-icons.el#28... Unfortunately, I don't have my windows machine at the moment so I won't be able to investigate this myself! But I'd be very interested in the profiling results :) |
This profile was created by moving the cursor up and down many times in the scratch buffer. |
(Can be opened with |
That's odd... It doesn't look like it's that intensive on the CPU, seeing as My intuition would tell me it's the way Windows Emacs does redisplaying... But I wouldn't know where to begin with it! I'll let you know if I get time to look into this... But I'm going to put it on hold from my perspective, sorry. |
I must admit, on MacOS Sierra, I also notice notable performance issues since I switched to spaceline-all-the-icons, especially when switching form a buffer to another of when creating a (built-in, not Will investigate. |
w.r.t. performance, unfortunately yeah there may be a bit of a performance hit with some of these segments... Since its evaluating a fair amount of lisp regularly, sometimes including IO operations! I don't know how often the mode line redraws - I know it definitely redraws when you switch buffer so that might be what you're seeing @jwintz. The best I can advise is customising it to your liking until your happy with performance. I work on a MacOS El Capitan and whilst it's sometimes noticeable compared to a vanilla mode line, it is doing and displaying a lot more information. I guess its all a trade off :) But I'm more than happy to accept performance improvements for segments! |
Hey @joncol I've been making a lot of performance improvements to this package (mainly through introducing memoization in |
@domtronn: Cool, I'll try it out (probably tomorrow) and let you know the results. |
@domtronn: I have to say that it's still very sluggish. The time from when I press a key to when something happens is something like 250 - 500 ms. |
Boooooo, that's unfortunate 😞 I don't suppose you could get a profile report for me for memory? That might tell me what Windows is struggling to do |
Attaching memory and cpu profile reports. The only thing I did during this profile was to move around the cursor. Hope it helps. |
Try to add this to your init: |
Same problem here on OSX 10.12.5 (16F73) and Emacs 25.2 with Spacemacs on latest develop branch. @Kungsgeten I've tried it here on OSX but I still experience noticeable lags even with cursor movements. |
I found the same thing - turns out is was a combination of For now I have disabled |
FYI - I pushed a change to projectile (bbatsov/projectile@7951b17) to cache |
I am experiencing the same issue on both macOS 10.12 and Windows 7, with GNU Emacs 25.2. spaceline-all-icons is very pretty but extremely laggy, no matter whether enabling |
FWIW, for me, that |
@braham-snyder - you're welcome - glad it was helpful to you. |
suggestion by @Kungsgeten fixed the performance issue for me. I was having trouble just navigating the buffer on windows 10 |
flydiff is still an issue on mac for me - #9 (comment) |
It causes a major performance penalty: domtronn/spaceline-all-the-icons.el#9
It causes a major performance penalty: domtronn/spaceline-all-the-icons.el#9
It causes a major performance penalty: domtronn/spaceline-all-the-icons.el#9
Hi,
When activating spaceline-all-the-icons on Windows (10) I get really slow performance. Just moving the cursor in the scratch buffer is slow.
No such problems on my Linux machine.
I'm using Emacs 25.1 in both cases.
Any idea what could cause this?
The text was updated successfully, but these errors were encountered: