In this article
Compare complete experiments under the same data-transfer and retention schedule. One visible GPU rate does not describe the full marketplace offer.
A Vast.ai experiment combines compute, storage and bandwidth costs. Hosts set offer terms, so inspect the detailed prices on the specific listing. A low GPU rate alone does not determine the cost of loading a large dataset or retaining files during a pause.
Save the offer you are evaluating
Record GPU model and quantity, disk allocation, storage terms, transfer rules and the time checked. The offer may differ when a later order is placed. Also save the maximum rental duration, since a suitable machine must cover preparation and export as well as computation.
Do not treat a previous session’s rate as a permanent tariff. A reproducible estimate identifies the actual offer and its assumptions, rather than assigning one timeless price to a GPU family.
Build the estimate from actions
Consider loading weights, running a series of jobs and exporting results. Each action belongs to a component of the estimate. Compute time, allocated capacity and transferred bytes are different inputs.
| Action | Input to record |
|---|---|
| Environment preparation | Billable time under the product rules |
| Input download | Volume and direction of transfer |
| Computation | Running time and rental type |
| Pause | Lifetime of retained storage |
| Export or migration | Output volume and overlapping resources |
Generation time is not automatically the entire session. Preparation and operator waiting can occupy a running resource even while the accelerator has little useful work.
Include the whole transfer route
If inputs are much larger than outputs, repeated downloads change the calculation. If outputs dominate, export matters more. State both volumes and repetitions so alternatives represent the same finished task.
The data-movement rules describe bandwidth charges with placement-dependent exceptions. Do not assume every instance-to-instance transfer is free. External source storage may also charge for its side of the route, so the GPU marketplace bill can represent only part of the complete transfer cost.
Reconcile a bounded pilot
Run a small representative session and save start, end, bytes moved and final instance state. Compare observed charges with the action table. Explain differences by resource or interval instead of silently increasing an unexplained contingency.
A prepared image may reduce setup effort, but no universal saving percentage follows. Keep documented billing rules, measured session behaviour and future assumptions separate. The estimate should answer what a finished experiment costs on your schedule; it does not establish income from operating your own GPU.
Turn the check into a practical next step
Compare complete experiments under the same data-transfer and retention schedule. One visible GPU rate does not describe the full marketplace offer.
For the documented details, consult the primary documentation; configuration reference. Continue with vast ai instance lifecycle stop destroy and vast ai copy data between instances.