Tool 003 · Data movement

How long will this dataset take to move?

Plan the payload, effective link rate, transfer window, destination copies, user-supplied costs, and twelve-month growth without uploading a file list.

StatusFree to use · browser-onlyEvery Run Any AI resource declares what is real today.

Current estimate

Dataset movement plan

Estimate wire time and storage from your own throughput and price assumptions—without uploading a manifest.

Dataset and copies
Network and user-supplied prices
Formula usedpayload = source TB × percent remainingseconds = payload bits ÷ (link Gbps × efficiency)

Storage multiplies the compressed payload by destination copies. Twelve-month growth compounds the entered monthly rate.

Read the result

Line rate is not transfer rate.

The calculator applies an explicit efficiency percentage to the link before estimating wire time. That keeps protocol overhead, competing traffic, throttling, and imperfect parallelism visible instead of quietly assuming a perfect network.

The result uses decimal TB and GB, matching common network and storage pricing units.

What should I use for link efficiency?

Use a measured sustained rate when possible. Otherwise choose a conservative percentage and run a second scenario for the likely range.

Does compression mean percentage saved?

No. The input is the percentage of data remaining after compression. If a 100 TB dataset becomes 70 TB, enter 70%.

Why count destination copies?

Training, validation, backup, and separate environments can multiply the storage footprint even though the network payload is transferred only once in this simple model.

What can make a real transfer slower?

Many small files, encryption, checksums, retries, source read speed, destination ingest limits, per-flow caps, shared links, and maintenance windows can all extend the schedule.