Jens Johansen
2cfc0146e1
This CL keeps slow (500+ ms) requests around for longer (to a total of 1000 of them), saves the start time of the request and prints a little more on the details page. The overall idea is that having a record of slow requests is better for debugging performance related issues than only having the newest 50 requests which basically requires one to "catch it" as it's being slow. Currently the 500 ms deadline for "slow" and 1000 requests saved was just grabbed from thin air; we can adjust them later if needed. Change-Id: Ib0d6e1fc2daad215d8745249abdc82f831a83785 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/279087 Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Jens Johansen <jensj@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
original protocol is specified in the file analysis_server/doc/api.html
and Language Server Protocol support is documented in
tool/lsp_spec/README.md.
Features and bugs
Please file feature requests and bugs at the issue tracker.