> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/definitions/throughput.md). # Throughput Throughput is defined as the number of pull requests you get through as a team over a selected period of time. ### Example If your team closed 4 pull requests on Monday, 2 on Tuesday, 6 on Wednesday, 0 on Thursday, and 8 on Friday, you would then see an average throughput of 4 pull requests a day for that week. ### Why it matters Throughput allows you to see the amount of work that is completed during a given time frame. A substantial increase in throughput means your teams are shipping more code. ### How to use it When looking at the throughput chart, the colors on the stacked bars represent the status of the pull requests opened on that specific day. We recommend focusing most on the yellow part. Seeing a lot of yellow in the past would indicate that on some days, we open a lot of pull requests but are just unable to get them in. In that case, it might make sense to focus on getting the old pull requests merged or closed before taking on more work. ### Where to find it You can find throughput in two places within Swarmia: * Pull Requests page * Insights → Code → Overview --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.swarmia.com/definitions/throughput.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.