Typescript server is slow on Zed when compared to VSCode

[baptisteArno]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

The coding experience in a large Typescript monorepo (https://github.com/baptisteArno/typebot.io) is still an issue for me even though it now uses the vtsls, I still don't get the same speed as VSCode or even NeoVim (with vtsls lsp)

I'm just helpless, what is doing Zed that could cause this code error refresh so slow?

This also can be linked with:

• A error diagnostic is shown even though LSP is not showing any error #18621

Environment

Zed: v0.156.0 (Zed Preview)
OS: macOS 15.0.0
Memory: 16 GiB
Architecture: aarch64

If applicable, add mockups / screenshots to help explain present your vision of the feature

VSCode:

CleanShot.2024-10-03.at.17.02.42.mp4

Zed:

CleanShot.2024-10-03.at.17.04.27.mp4

If applicable, attach your Zed.log file to this issue.

No response

[osiewicz]

Could you also record a comparison with Neovim + VTSLS? VSC uses tsserver directly.

[baptisteArno]

CleanShot.2024-10-03.at.19.57.36.mp4

LazyVim distro with that lsp config override:

return {
  "neovim/nvim-lspconfig",
  opts = function(_, opts)
    opts.inlay_hints.enabled = false
    opts.servers.vtsls.settings.typescript.tsserver = {
      experimental = {
        enableProjectDiagnostics = false,
      },
    }

    opts.servers.vtsls.autoUseWorkspaceTsdk = true

    return opts
  end,
}

[baptisteArno]

But as you can see in Zed, I'm hovering my mouse over the sessionState variable and it gives me the proper type so I guess that the LSP is up to date but Zed decides not to update the diagnostic overlay directly?

[juanpmarin]

Same issue here, I'm running zed on fedora linux

[chungweileong94]

Been facing the same issue for the past few months. The only workaround right now is to restart the LSPs once in a while.

[chungweileong94]

I found this PR from vtsls. It seems Electron came with an unofficial Node version that came with pointer compression, which is also what VSCode is using. I played with it for a while. It does seem like the memory is relatively smaller, but I haven't really started coding with it.

Screen.Recording.2024-11-07.at.9.49.32.PM.mov

[UPDATE] After trying to open files from at least 10 different sub-repos, I can see the tsserver memory usage cut nearly half, from 3GB~ down to 1GB~.

[chungweileong94]

I'm not sure if this is good enough to reproduce the problem, but if you have a really large monorepo, try opening multiple files from multiple different sub-repos, and you will start noticing that the node memory usage will start to build up, which I think tsserver will likely get slow and unusable like the issue described.