Continuous Integration (CI) is crucial in modern software development, primarily by automating checks on Pull Requests to free engineers for more nuanced tasks, yet the duration of CI processes has become a subject of debate. While a 10-minute CI cycle is often cited as ideal, Graphite's data-driven analysis reveals that CI times between 15-30 minutes may correlate with higher productivity in terms of merged Pull Requests, suggesting that slightly longer CI times might not necessarily hinder development efficiency. The study found that longer CI times increase the time to merge due to repeated cycles, which can accumulate to significant delays, and highlights that CI times exceeding 30 minutes may require optimization. The concept of stacking workflows, where changes are broken into smaller, parallel PRs, is recommended to alleviate CI delays, maintaining development velocity despite lengthy CI runs. The data suggests a nuanced understanding of CI times, advocating for a balance between speed and complexity, with an emphasis on adapting CI practices to optimize productivity effectively.