# Throughput ### 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: 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: ``` GET https://help.swarmia.com/definitions/throughput.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.