Stream: t-compiler/rust-analyzer

Topic: slow typing

Laurențiu (Jul 24 2019 at 08:03, on Zulip):

How can I debug slowness while typing? The status panel doesn't show any long-running requests

Laurențiu (Jul 24 2019 at 08:04, on Zulip):

where does the output of RA_PROFILE go?

matklad (Jul 24 2019 at 08:05, on Zulip):

Hm, we don't intersect any typing except for \n. If general typing is slow, that probably means that a problem is either withing the editor (perhaps some run-away extension?) or is due to the generally high load (I get slow tying when I compile rustc in the background :))

matklad (Jul 24 2019 at 08:05, on Zulip):

The output of RA_PROFILE goes to stderr

Laurențiu (Jul 24 2019 at 08:05, on Zulip):

Also . for completion, I think?

matklad (Jul 24 2019 at 08:05, on Zulip):

The editors usually have some way to see server's stderr. for VS Code, it's in the Output tab in the panel

matklad (Jul 24 2019 at 08:06, on Zulip):

well, we do intercept = and ., but for formatting on typing requests, and they should be non-blocking

Laurențiu (Jul 25 2019 at 05:21, on Zulip):

Yeah, I'm not sure if it's RA or something else, but Code ends up being unbearably slow for me. I think it's the main Chrome process that ends up eating a little over one full CPU while I'm typing.

Laurențiu (Jul 25 2019 at 05:23, on Zulip):

There's nothing in the RA profile that takes more than 60ms or so (diagnostics are the slowest), but it takes some 3-500ms to display the letters that I'm typing

uni (Jul 25 2019 at 07:57, on Zulip):

do you use vscodevim?

Laurențiu (Jul 25 2019 at 07:57, on Zulip):


Last update: Jul 27 2021 at 21:45UTC