ETL Throughput Calculator

Step-by-Step Guide

1. 1Choose a Calculation Mode: Select Records Throughput, Data Size Throughput, Completion Time, or Capacity Planning depending on your question.
2. 2Try an Example (Optional): Click Large Batch Job, Fast Ingestion Job, or File Transfer Pipeline to instantly load realistic sample figures.
3. 3Enter Your Pipeline Figures: Type your records, data size, or processing speed, and select matching time and data units. Results update instantly with a 150ms debounce.
4. 4Use Swap Unit for Quick Conversion: Click Swap Unit to cycle the time unit between seconds, minutes, and hours without retyping your value.
5. 5Review Throughput and Capacity: Check records/sec or MB/sec, plus hourly, daily, weekly, and monthly capacity projections.
6. 6Check the Throughput Trend Chart: See a visual projection of cumulative volume processed across the pipeline's run window.
7. 7Compare, Export, or Share: Set a Current and an Optimized scenario to compare side by side, export as CSV or JSON, print a formatted report, or copy a shareable URL.

Key Features

• ✓4 calculation modes: Records, Data Size, Completion Time, Capacity Planning
• ✓Automatic time unit (seconds/minutes/hours) and data unit (MB/GB/TB) conversion
• ✓Records/sec, /min, /hour plus daily, weekly, and monthly capacity
• ✓Data throughput with hourly, daily, weekly, and monthly capacity
• ✓Color-coded performance rating (🔴 Low, 🟡 Good, 🟢 Excellent)
• ✓SLA sufficiency check with growth-adjusted capacity projection
• ✓Interactive throughput trend chart
• ✓Current vs. Optimized scenario comparison
• ✓Shareable calculation URL using query parameters
• ✓Export report as CSV or JSON with full breakdown
• ✓Print-ready formatted report
• ✓Copy full report to clipboard in one click
• ✓Calculation history — save and reload up to 20 past results
• ✓No signup required — 100% free to use
• ✓All processing runs locally — no data leaves your browser

Pro Tips

• 💡Measure throughput using wall-clock execution time, not just active processing time — idle time waiting on upstream sources or downstream writes is still part of your real pipeline runtime.
• 💡Use Capacity Planning mode's growth percentage to stress-test your pipeline before a known traffic event, rather than discovering an SLA breach during it.
• 💡Track throughput over multiple runs rather than a single measurement — batch jobs can vary run to run due to source data skew, cluster load, or network conditions.
• 💡Use Current vs. Optimized comparison when evaluating a proposed pipeline change — a side-by-side throughput comparison makes the expected improvement concrete before you invest engineering time.
• 💡When reporting data throughput, always confirm whether "GB" refers to binary (1024-based) or decimal (1000-based) units — this calculator uses the binary standard consistently.

Common Mistakes to Avoid

• ✕Don't compare records/sec across pipelines with very different record sizes — a pipeline moving small clickstream events will naturally show a higher records/sec than one moving large document records, even at similar data throughput.
• ✕Don't plan capacity using only average load figures — peak load, not average load, is what determines whether an SLA is met during the busiest periods.
• ✕Don't assume completion time scales linearly for every pipeline — some jobs have fixed overhead (connection setup, schema validation) that doesn't shrink proportionally as processing speed improves.
• ✕Don't ignore the growth-adjusted capacity check — a pipeline that meets today's SLA can silently become insufficient as data volume grows if capacity isn't re-evaluated periodically.
• ✕Don't mix up MB/sec (throughput) with Mb/sec (megabits per second, common in networking) — this calculator consistently uses megabytes.