Storage Throughput Estimator
This tool continues the Compute design flow
Use this step to verify whether sequential transfer demand becomes the next real limiter after random IOPS demand has already been established.
This is where block size, read/write mix, transfer overhead, and storage path width turn into a real throughput target instead of a generic “fast enough” assumption.
Best for: identifying when storage throughput becomes the limiting factor even if IOPS appears sufficient.
🔒 Locked
This tool is included with Pro access for this category.
What this models
- Estimated MB/s demand from IOPS, block size, and read/write mix
- Whether transfer pattern is random, mixed, or sequentially throughput-heavy
- How protocol and filesystem overhead change usable bandwidth headroom
Inputs
Results
Model: throughput is estimated from IOPS, block size, read/write ratio, and protocol overhead. This is a planning view for transfer demand, not a replacement for traced workload captures.
Export Report
Add optional project context and generate a clean documentation view that can be printed or saved as a PDF for client or internal use.