Closed Levitanus closed 1 year ago
LSP just creates Phantoms
using ST's API and then it's up to ST to render them as efficiently as possible. So it's likely nothing that we can do about.
I did test using pretty extreme case and did get worse results but not as bad as you:
Frame time exceeded 60hz: 23ms
Frame time exceeded 60hz: 18ms
fps: 80.6 average: 8ms
fps: 63.4 average: 11ms
fps: 66.1 average: 10ms
fps: 64.8 average: 9ms
Frame time exceeded 60hz: 17ms
Frame time exceeded 60hz: 18ms
vs. no phantoms:
fps: 68.7 average: 3ms
fps: 80.8 average: 3ms
fps: 63.5 average: 4ms
fps: 64.2 average: 4ms
This is on a standard Macbook M1 and 1440 screen vertical resolution.
This can of course vary per GPU, CPU and OS. In any case, this is something that should be reported to ST (https://github.com/sublimehq/sublime_text/issues/new/choose), if not already. Though it would be more likely to looked at if it can be reproduced easily.
Maybe at least show screen recording so that we know what you are looking at. There might be something specific that causes worse performance.
Thank you, let's close it here :)
I'm not sure if this is an issue of the plugin itself, but not LSP total. As, I turned back from VSCode to ST4 exactly, as it was not so responsive, as ST. But, after a couple of days of rust programming in ST, I missed inlay hints, so, turned them on. This dramatically decreased response time of the editor (probably, fps). Currently, I see no exact reason for such behavior, but it presents.
This «freezing» is not dependent on timeout preferences:
FPS while displaying hints:
And while not:
Plugin Event Profile: