summaryrefslogtreecommitdiff
path: root/cli/bench/lsp.rs
AgeCommit message (Collapse)Author
2024-10-16Reland feat(lsp): deno/didRefreshDenoConfigurationTree notifications (#26325)Nayeem Rahman
2024-08-24refactor(lsp): changes for lsp_types 0.97.0 (#25169)Nayeem Rahman
2024-04-17chore(lsp): Include new benchmark in the collected benchmark data (#23420)Nathan Whitaker
So it will actually show up on the [deno benchmarks site](http://deno.com/benchmarks)
2024-04-16chore(lsp): Add benchmark for performance on a large real-world repo (#23395)Nathan Whitaker
This PR adds a benchmark intended to measure how the LSP handles larger repos, as well as its performance on a more realistic workload. The repo being benchmarked is [deco-cx/apps](https://github.com/deco-cx/apps) which has been vendored along with its dependencies. It's included as a git submodule as its fairly large. The LSP requests used in the benchmark are the actual requests sent by VSCode as I opened, modified, and navigated around a file (to simulate an actual user interaction). The main motivation is to have a more realistic benchmark that measures how we do with a large number of files and dependencies. The improvements made from 1.42 to 1.42.3 mostly improved performance with larger repos, so none of our existing benchmarks showed an improvement. Here are the results for the changes made from 1.42 to 1.42.3 (the new benchmark is the last one listed): **1.42.0** ```test Starting Deno benchmark -> Start benchmarking lsp - Simple Startup/Shutdown (10 runs, mean: 379ms) - Big Document/Several Edits (5 runs, mean: 1142ms) - Find/Replace (10 runs, mean: 51ms) - Code Lens (10 runs, mean: 443ms) - deco-cx/apps Multiple Edits + Navigation (5 runs, mean: 25121ms) <- End benchmarking lsp ``` **1.42.3** ```text Starting Deno benchmark -> Start benchmarking lsp - Simple Startup/Shutdown (10 runs, mean: 383ms) - Big Document/Several Edits (5 runs, mean: 1135ms) - Find/Replace (10 runs, mean: 55ms) - Code Lens (10 runs, mean: 440ms) - deco-cx/apps Multiple Edits + Navigation (5 runs, mean: 11675ms) <- End benchmarking lsp ```
2024-01-01chore: update copyright to 2024 (#21753)David Sherret
2023-10-25build: fix lsp benchmark (#20969)Nayeem Rahman
2023-05-26chore(lsp/tests): diagnostic synchronization (reland) (#19270)David Sherret
Merge on approval as it fixes the flaky test.
2023-03-09refactor(tests/lsp): consolidate more into test LspClient and reduce ↵David Sherret
verbosity (#18100)
2023-03-08refactor(lsp): improve test client initialization (#18015)David Sherret
2023-01-27chore: upgrade to Rust 1.67 (#17548)David Sherret
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
2023-01-02chore: update copyright year to 2023 (#17247)David Sherret
Yearly tradition of creating extra noise in git.
2022-06-28refactor(bench): continuous benchmarking improvements (#14821)Divy Srivastava
2022-04-03refactor(lsp): migrate from lspower back to tower-lsp (#14163)Jason
2022-03-30feat(lsp): add experimental testing API (#13798)Kitson Kelly
Ref: denoland/vscode_deno#629
2022-03-23chore: remove all `pub(crate)`s from the cli crate (#14083)David Sherret
2022-01-13chore: rename cli/bench/fixtures to cli/bench/testdata (#13363)Ryan Dahl
2022-01-07chore: update copyright to 2022 (#13306)Ryan Dahl
Co-authored-by: Erfan Safari <erfanshield@outlook.com>
2021-06-05fix(lsp): refactor, fix issues and add benchmark for code lens (#10841)Kitson Kelly
2021-05-20fix(lsp): re-enable the per resource configuration without a deadlock (#10625)Kitson Kelly
Fixes #10603
2021-05-18refactor: share test harness for lsp between bench and integration (#10659)Kitson Kelly
2021-05-12fix(#10603): revert minimal changes to resolve deadlock bug (#10605)Kitson Kelly
2021-05-10feat: support workspace folders configuration (#10488)Kitson Kelly
Ref #8643
2021-05-07refactor(lsp): publish diagnostics independently (#10525)Kitson Kelly
Resolves #10518
2021-03-25upgrade: Rust 1.51.0 (#9895)Yusuke Tanaka
2021-02-25test(lsp): add benchmarking tests (#9586)Kitson Kelly
Co-authored-by: Ryan Dahl <ry@tinyclouds.org>