LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Jira best practices
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration
    • Creating & managing teams
      • Teams API
    • Managing users and roles
    • Organization settings
      • Jira setup
      • Data quality
        • Pull request data quality
        • Linking pull requests to issues
      • Investment balance
      • Deployments
        • Generate deployments from merged pull requests
        • Generate deployments from GitHub deployments
        • Generate deployments from GitHub checks
        • Generate deployments via the API
          • Generate deployments for monorepos via the API
    • Team settings
      • Mapping work to your team
      • Sprints
      • Team notifications
    • Notifications
      • Personal notifications
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Retrospective guide
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Working agreements
    • Set up working agreements
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Example
  • Why it matters
  • How to use it
  • Where to find it

Was this helpful?

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

PreviousChange failure rateNextTime to deploy

Last updated 1 month ago

Was this helpful?