Repository Growth Calculator
Calculate a repository's monthly growth rate from historical size data and project its size at a future date.
Inputs
Repository size at the start of the measured period.
Repository size now.
Time elapsed between the initial and current measurements.
How many months into the future to project size.
Growth per Month
100.0MB/mo
Projected Size
2.54GB
Monthly Growth Rate
12.50%
Projected Size
2,600MB
Step by step
Growth per month
(1400 - 800) / 6
= 100.0MB/mo
Projected size in the future
1400 + 100.0 × 12
= 2600MB
How it works
Assuming linear growth, a repository's size trend can be extrapolated forward. Formula: growth_per_month = (current_size − initial_size) / months, then projected_size = current_size + growth_per_month × projection_months. This is a simple linear model — actual growth is often stepped (large binary commits, LFS migrations) rather than smooth, so treat projections as a planning floor, not a guarantee.
Formulas
Growth rate
growth_per_month = (current_size - initial_size) / elapsed_months
- current_size
- Current repository size (MB)
- initial_size
- Initial repository size (MB)
- elapsed_months
- Months between measurements
Projected size
projected_size = current_size + growth_per_month × projection_months
- current_size
- Current repository size (MB)
- growth_per_month
- Monthly growth rate (MB)
- projection_months
- Months to project forward
Frequently Asked Questions
Is linear extrapolation accurate for repository growth?
Only roughly — repository growth is often bursty (a single commit adding a large dataset, or a history-rewrite reducing it sharply). Use this as a capacity-planning baseline and revisit it periodically with fresh measurements.
What should I track over time to feed this calculator?
Periodic snapshots of `du -sh .git` (or your Git host's repo size API) at consistent intervals give you the initial/current size pair to compute a real growth rate.
How can I slow repository growth?
Move large binaries to Git LFS, add generated artifacts to .gitignore before they're ever committed, and periodically run history-rewriting cleanups for accidentally committed large files.
Does growth rate change over a project's lifecycle?
Yes — early-stage projects often grow faster as scaffolding and dependencies are added; mature projects tend to plateau unless a major asset migration or history rewrite changes the trend.