performance degradation when working with large files in JS #1274
Replies: 1 comment 1 reply
-
There's an issue about this already, but your post gave me a clue about the source #1115 (comment) so thank you! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I didn't make this an issue as it seems that this only occurs for selected few people when working with JS projects.
First I was concerned that It was some misconfiguration on my end but after a post on Reddit it seems that other people are suffering the same issues.
I am using LazyVim and when working in a JS file I have
vtsls
eslint
tailwindcss_language_server
andemmet_language_server
attached to buffer.blink.cmp
seems to struggle with files with above 2k LOC and part of this problem is also the LSPs but the difference in time for drawing the menu is far more then compared tonvim.cmp
.The most throttling that
blink.cmp
gets is fromemmet_language_server
and it cannot seem to handle those completions.The delay in drawing a menu is large enough that I have to stop typing wait for the menu and then continue and could honestly type faster and I'm not that fast to begin with.
This is the post on Reddit that some other people have similar experiences as well.
While
vtsls
andemmet_language_server
might be the reasons for alot of this throttling in getting completions it should atleast draw the menu and show the buffer sources instead of blocking the whole menu.This could be an issue in terms of configuration as I'm not that well aware of what
LazyVim
is doing withblink.cmp
as I just recently switched over.Any help regarding this would be very helpful.
In any other filetype
blink.cmp
has been miles abovenvim.cmp
for me so thank you for your amazing work!Beta Was this translation helpful? Give feedback.
All reactions