> For the complete documentation index, see [llms.txt](https://docs.loci-dev.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loci-dev.net/loci-inspector/execution-metrics-worst-case-response-throughput-and-bottleneck-chart.md).
# Execution Metrics Worst-Case Response, Throughput & Bottleneck \[Chart]
The chart identifies functions with the greatest absolute change in execution/response time between two points of comparison (Target and Base) — for example different builds, configurations, or code versions. The change is measured in delta units of time (not percentages) to emphasize functions that have the most impact on overall performance shifts, regardless of their relative size. This helps you quickly spot which parts of the codebase have regressed or improved the most in terms of raw throughput (for example, total execution time).
To keep the report focused on significant performance changes, only functions with a time deviation greater than 100 nanoseconds are visualized. This threshold filters out minor fluctuations that are unlikely to meaningfully affect overall performance, helping you concentrate on the most critical regressions or optimizations.
## Filters implemented on the Report
* Binaries: Select All or a specific binary
* Status: All, Modified, New, Removed, Unchanged
* Filter Functions: Search a function and filter it in the report
* Timing displayed: Responce, Throughput, or Bottleneck
Notes on conditional display:
* If there is only one version uploaded (Target), the “Functions” filter is not shown.
* If there is only one binary in the version, the “Binaries” filter is not shown.
Single version - greatest absolute change in execution time
Comparing two versions (Base and Target) - greatest absolute change in execution time
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.loci-dev.net/loci-inspector/execution-metrics-worst-case-response-throughput-and-bottleneck-chart.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.