aboutsummaryrefslogtreecommitdiff
path: root/docs/dev/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/dev/README.md')
-rw-r--r--docs/dev/README.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 991deaf90..ba24524f2 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -113,7 +113,7 @@ communication, and `print!` would break it.
113If I need to fix something simultaneously in the server and in the client, I 113If I need to fix something simultaneously in the server and in the client, I
114feel even more sad. I don't have a specific workflow for this case. 114feel even more sad. I don't have a specific workflow for this case.
115 115
116Additionally, I use `cargo run --release -p ra_cli -- analysis-stats 116Additionally, I use `cargo run --release -p ra_lsp_server -- analysis-stats
117path/to/some/rust/crate` to run a batch analysis. This is primarily useful for 117path/to/some/rust/crate` to run a batch analysis. This is primarily useful for
118performance optimizations, or for bug minimization. 118performance optimizations, or for bug minimization.
119 119
@@ -157,7 +157,7 @@ There's also two VS Code commands which might be of interest:
157 157
158# Profiling 158# Profiling
159 159
160We have a built-in hierarchical profiler, you can enable it by using `RA_PROF` env-var: 160We have a built-in hierarchical profiler, you can enable it by using `RA_PROFILE` env-var:
161 161
162``` 162```
163RA_PROFILE=* // dump everything 163RA_PROFILE=* // dump everything
@@ -165,17 +165,17 @@ RA_PROFILE=foo|bar|baz // enabled only selected entries
165RA_PROFILE=*@3>10 // dump everything, up to depth 3, if it takes more than 10 ms 165RA_PROFILE=*@3>10 // dump everything, up to depth 3, if it takes more than 10 ms
166``` 166```
167 167
168In particular, I have `export RA_PROFILE='*>10' in my shell profile. 168In particular, I have `export RA_PROFILE='*>10'` in my shell profile.
169 169
170To measure time for from-scratch analysis, use something like this: 170To measure time for from-scratch analysis, use something like this:
171 171
172``` 172```
173$ cargo run --release -p ra_cli -- analysis-stats ../chalk/ 173$ cargo run --release -p ra_lsp_server -- analysis-stats ../chalk/
174``` 174```
175 175
176For measuring time of incremental analysis, use either of these: 176For measuring time of incremental analysis, use either of these:
177 177
178``` 178```
179$ cargo run --release -p ra_cli -- analysis-bench ../chalk/ --highlight ../chalk/chalk-engine/src/logic.rs 179$ cargo run --release -p ra_lsp_server -- analysis-bench ../chalk/ --highlight ../chalk/chalk-engine/src/logic.rs
180$ cargo run --release -p ra_cli -- analysis-bench ../chalk/ --complete ../chalk/chalk-engine/src/logic.rs:94:0 180$ cargo run --release -p ra_lsp_server -- analysis-bench ../chalk/ --complete ../chalk/chalk-engine/src/logic.rs:94:0
181``` 181```