Ceph Repo Dora Metrics: Solid Deployments, but First Response and Merge Times Are Dragging

Imagine you're managing a growing tech platform, and every day, your users generate terabytes of data—files, logs, videos, backups, etc. As your business expands, so do your storage needs, and suddenly, traditional storage solutions aren’t cutting it anymore. You need something that scales seamlessly, performs reliably, and won’t blow your budget.

This is where Ceph steps in.

Ceph is an open-source, software-defined storage system designed to handle massive amounts of data with ease. It offers a unified platform that supports object, block, and file storage—making it incredibly versatile for various use cases.

Using Middleware OSS, we did some snooping around their software delivery workflow. We checked the Dora Metrics. Dora metrics are four key indicators—Deployment Frequency, Lead Time for Changes, Mean Time to Restore (MTTR), and Change Failure Rate—used to measure the efficiency, speed, and stability of software delivery in DevOps practices.

Also read: Middleware: Open-Source Dora Metrics for a Smoother Engineering Flow

Ceph Repository: Speeding Ahead but Stalling at Key Turns

The Ceph repository tells a story of both brilliance and bottlenecks. At first glance, the numbers are dazzling: 294 pull requests merged in July 2024 and deployment frequency consistently above 50 per month—a mark aligned with top-tier benchmarks from the 2023 State of DevOps report.

Fast Deployments—A Sign of CI/CD Maturity

One thing is clear: Ceph’s deployment frequency is a triumph. Regular deployments indicate an efficient continuous integration/continuous deployment (CI/CD) system capable of rapid iteration. When pull requests are merged frequently, it signals not just activity but agility. For example, pull requests like PutACL Replication for RGW Multisite PR #58545 and Enhanced RGW Sync Flow PR #58544 highlight how the repository actively evolves, refining critical features through quick deployments.

This pace isn’t accidental—it’s evidence of just-in-time feedback and efficient collaboration. However, frequent deployments only reveal part of the picture.

Also read: Deployment Frequency 101: Leverage DORA Metrics to Improve Software Delivery

Feature Work, Testing, and Documentation: A Healthy Mix

The Ceph repository isn’t just about high deployment velocity. It also reflects a balanced blend of contributions:

• 40% feature development

• 30% testing and QA

• 30% documentation efforts

This diversity is crucial in any mature repository, ensuring that both innovation and maintenance move forward. For instance, recent improvements such as performance fixes for Radosgw PR #58491 by cbodley: show Ceph's focus on optimization, while testing enhancements PR #58445 and documentation updates PR #58452 highlight the team’s attention to both quality and clarity.

Strengths of the Ceph Repository

• Exceptional Deployment Frequency
  Over 50 deployments per month, aligning with the gold standard set by the 2023 State of DevOps report. July alone saw an impressive 294 merged pull requests.

• Diverse and Active Contributions
  The repository maintains a healthy split—40% feature work, 30% testing, and 30% documentation updates—ensuring balanced development. Significant PRs like #58545.(PutACL Replication for RGW Multisite) by smanjara and #58544 (Enhanced RGW Sync Flow) by nmunet exemplify this diversity.

• Robust CI/CD Pipeline
  The rapid deployment cadence reflects a mature CI/CD system capable of quick iterations and just-in-time feedback, contributing to frequent, stable updates.

• Engagement from a Large Contributor Base
  With 1,359 contributors, the Ceph project benefits from a wide range of expertise, ensuring continuous innovation across multiple areas.

The Silent Roadblocks: How Slow Response and Merge Times Stall Progress

However, scratch beneath the surface, and there are signs of friction. First Response Times (FRT) and merge times suggest opportunities for optimization in areas that directly impact contributor satisfaction and workflow efficiency.

Despite impressive deployment numbers, Ceph shows signs of strain in its First Response Time (FRT) and merge processes. With an average FRT of 38 hours in July, improving only to 28 hours by September, contributors might feel they are left hanging.

In open-source communities, speedy responses matter. Timely acknowledgment of pull requests can be the difference between retaining contributors or losing them to other projects. Contributors thrive on feedback loops that are swift and constructive, ensuring their work feels valued.

The merge times are another area of concern.

While July and September saw merge times of around 45 hours, the jump to 68 hours in August reveals potential bottlenecks in code reviews or approvals.

Delayed merges mean developers could be stuck in limbo, waiting for their work to become part of the product. This slows down progress and discourages participation—an area Ceph cannot afford to overlook, especially with 1,359 contributors fueling the project.

Recommendations: Leveraging Strengths for Greater Impact

1. Use Deployment Velocity to Improve Contributor Experience

Since the CI/CD system is already efficient, Ceph could integrate automated responses or bots to acknowledge new contributions instantly. This would address the lag in First Response Time (currently averaging 28-38 hours), keeping contributors engaged.

2. Channel Contribution Diversity into Specialized Review Teams

Given the active mix of feature, testing, and documentation work, Ceph could create dedicated review teams for each type. This would streamline Merge Times (which reached 68 hours in August) by reducing bottlenecks in the code review process.

3. Turn High Contributor Engagement into Mentorship Opportunities

With such a large contributor pool, Ceph could formalize mentorship programs, encouraging seasoned contributors to guide newcomers. Faster onboarding will boost active participation and help sustain long-term engagement.

4. Optimize Feedback Loops with Targeted Testing

   With 30% of contributions focused on testing, Ceph can further accelerate releases by expanding pre-merge testing coverage. This will reduce delays during the review process, ensuring Merge Times align with the project's deployment speed.

5. Maximize Global Community Engagement

   By leveraging events like Ceph Day and Ceph User Summit, Ceph can foster greater collaboration among contributors. Hosting workshops or discussion panels focused on improving response and merge times could directly address these challenges while strengthening community ties.

Also read: Django Dora Metrics: Strong Cycle Time, Room for Improvement in Merged PRs

Ceph Repo Dora Metrics: Solid Deployments, but First Response and Merge Times Are Dragging

The Ceph repository demonstrates remarkable strengths—high deployment frequency, diverse contributions, and robust community engagement. However, the hidden bottlenecks in response and merge times create friction that can undermine the very agility its CI/CD pipeline promises.

If you are looking to improve your engineering pipeline, then write to us at productivity@middlewarehq.com and we would be happy to help you provide actionable insights into your workflow or you can also try tracking your Dora metrics yourself using Middleware Open Source that too for free!

Did you know?

Ceph was created by Sage Weil as part of his doctoral thesis at the University of California, Santa Cruz, in 2004. It has since evolved into a robust, open-source storage solution.

Further Resources

Middleware and Dora Metrics

Continuous Integration Guides

Dora Metrics Methodology

Ceph Documentation