You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* forgotten-logging-can-be-painful
Forgotten logging after debugging of LSP problems can cause problems as well
* Update docs/page/performance.md
* Update docs/page/performance.md
Copy file name to clipboardExpand all lines: docs/page/performance.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,16 @@ Also you can disable the file watch feature with:
54
54
(setq lsp-enable-file-watchers nil)
55
55
```
56
56
57
+
## Check if logging is switched off.
58
+
59
+
Make sure `lsp-log-io` is `nil`. You might have forgotten it after a debugging session, for example. It can cause a great performance hit.
60
+
61
+
```elisp
62
+
(setq lsp-log-io nil) ; if set to true can cause a performance hit
63
+
```
64
+
65
+
Sometimes you might need to check logging for specific LSP server configuration as well, i.e. for `lsp-eslint` it is: `lsp-eslint-trace-server`.
66
+
57
67
## Reporting performance problems
58
68
59
69
If you have tried all of the non-optional steps from the list and `emacs` is still not very responsive please open a PR with the following information:
0 commit comments