Closed
Description
Right now, we invalidate metadata on every keystroke, and for a go.mod
file, that means that the metadata for the entire workspace is invalidated as you type. This triggers a go list
on every keystroke, causing CPU usage to spike. We need to improve the UX of editing a go.mod
file by hand, and that likely will be resolved by only invalidating metadata on go.mod
saves, not edits.
#42266 might also be helpful, though I don't think it's the critical issue.