I installed atom and juno plugins, and the REPL console subwindow is very slow at scrolling and everything related, such as executing new commands there. A key/mouse press is reflected only after a few seconds. All other panels work fine, and an almost equivalent installation at another computer (both have i3 as window manager and similar overall setup) is fast even for REPL. I didn’t use atom before, so it’s a fresh installation. Any ideas how to track and fix the cause of slow REPL?
My recommendation is to just use i3 instead of atom. If you already use i3, why do you need a program like atom to emulate its workflow? When i switched to i3, i completely ditched atom.
What do you mean? i3 is a window manager, atom is an ide - how are they related?
With the Julia REPL and vim editor and i3, the setup is basically same as atom IDE, except faster since it doesnt require electron. Vim plugins give me auto completion, etc.
I guess if you dont use vim, then maybe not.
Please don’t derail the thread like this. The question was about Atom being slow and talking about how Vim can also do autocompletion is completely unhelpful and unrelated.
8 Likes
I’m sorry you see it as unrelated, but based on my experience, it is very related. The OP specifically mentions i3, so it is a relevant work around and can solve the problem of sluggish response time
Is Atom slow by default (i.e. with no plugins installed) or is it only after adding juno & co?
It is not that “atom is slow”, only the REPL panel is slow! Code editing, for example, works fine.
Try the Fallback Renderer option in the julia-client settings:
I’ll add a FAQ entry to increase visibility for that. In theory we could also detect this happening and open a popup (like VSCode does), but I haven’t yet found the time to implement that.
As to why this happens: The default REPL terminal renderer in Atom heavily relies on good GPU support, so minor hiccups your graphics driver might have (e.g. an improper setup, or just your laptop going to sleep and waking up again sometimes) might cause drastic performance issues.
2 Likes
It turned out the issue was somehow related to me installing atom through snap. Now I installed it from downloadable deb package from the website and everything works ok regarding performance. Of course, this way I lose auto updating, but this is less of an issue.
Had the same issue, the Fallback Renderer option solved it. But then, what’s the “default” and the “fallback” renderers? How do they differ from each other? This could lead to the source of the problem…
Funny thing is, I have Juno running on 2 Windows 10 machines, and on one Ubuntu 18.04 machine. I only experience the sluggish REPL on one of the Windows 10 machines.
The “fallback” renderer as just a normal DOM-based renderer, while the “default” one is GPU accelerated (and therefore quite a bit faster).
So yeah, any problems you might have with your graphics drivers might kill the default renderer’s performance.
The “Fallback renderer” option worked for me. If it’s of any relevance. I have a GeForce 940M and I have had troubles with my graphic card on Linux Mint 19, so much so that switching to the integrated graphics crashes the computer, so I’m permanently on the 940M…