> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/metrics-and-definitions/throughput.md).

# Throughput

<figure><img src="/files/aEapUnp7wtPT9Nq8r0n6" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ENYPY8NDhbkX7UcCsI8h" alt=""><figcaption><p>Throughput screen measures volume of work </p></figcaption></figure>

#### These are the metrics present in this section:

* **Average PR size** :  Average number of lines modified during a selected time period
* **Commits**: Number of commits pushed.
* **PRs Open**:  Pull Requests (PR) opened during the selected time period.
* **PRs Merged**: The number of PR merged in the selected time period.
* [<mark style="color:purple;">**New Work%**</mark>](/metrics-and-definitions/throughput/new-work.md): It shows the total lines of code added or modified.
* **Closed Issue Count** : Number of issues closed&#x20;
* **Completed story points : Number of** story points completed
* [<mark style="color:purple;">**Active Days**</mark>](/metrics-and-definitions/throughput/how-are-active-days-calculated.md):  Average number of days in a week that a user/team is active on GIT.&#x20;
* **Codebase Changes** : The lines of code that were added , removed or modified.
* **Review Breakdown**: PRs reviewed by selected authors during the selected time period.
* **Merge Breakdown:** PRs merged by selected authors during the selected time period.

#### Related articles

{% content-ref url="/pages/91BMQcOmKybomkJc4cGh" %}
[How to improve planning and throughput](/improve-performance/how-to-improve-planning-and-throughput.md)
{% endcontent-ref %}

{% content-ref url="/pages/NH67ZVY1tg8KRArK9EUv" %}
[How to track, manage, and reduce technical debt?](/improve-performance/how-to-track-manage-and-reduce-technical-debt.md)
{% endcontent-ref %}

{% content-ref url="/pages/XtcnkpSORD6EHmnzIbFq" %}
[Why do some metrics like PRs reviewed or merged have more than 100%?](/faqs/metrics-and-data-faqs/why-do-some-metrics-like-prs-reviewed-or-merged-have-more-than-100.md)
{% endcontent-ref %}


---

# 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.hivel.ai/metrics-and-definitions/throughput.md?ask=<question>&goal=<endgoal>
```

`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.