
NVIDIA / Volta
V100 SXM3 32GB
| Provider / plan | Price / GPU-hour | Rental type | Terms & configuration | Last checked | Provider pricing link |
|---|---|---|---|---|---|
| CloudRiftBest on-demand | Unavailable | On-demandNo reservation | 1 GPU minimumNot specifiednoneView detailsAPI list rate; whole-instance charge retained separately. Availability is a point-in-time observation; reservations are not provided by this endpoint.
|
2026-11-22Auto-collected | View pricing ↗ |
Prices are dated listings, not live availability. Compare minimum GPU counts and commitments. Storage, networking and taxes may add charges; CPU/RAM inclusion depends on the provider and is shown beside each serverless rate.
V100 SXM3 32GB rental prices on xpu live are linked to CloudRift. This hardware profile records 32 GB of HBM2 memory and the Volta architecture. Use this page to compare the exact allocation with its provider offers and source dates.
V100 SXM3 32GB specifications and edition
32 GB SXM3 configuration. V100 SXM2, SXM3 and PCIe allocations have separate source identities and rental listings. SXM3 is the provider-reported DGX-2-era V100 form; the image is identified as a V100 module family reference, not an exact host-board inspection.
The recorded form factor is SXM3. These are hardware specifications; the rented host’s CPU, RAM, disk and network allocation are separate resources. Review the offer details for the actual server configuration.
Where to rent V100 SXM3 32GB
Compare CloudRift in the rental table. Prices are received by the pricing service and linked to this GPU record. A timestamp identifies the observation used for each listing. A missing or unavailable offer does not mean the hardware is free; it means no eligible active price is available in that listing.
For an hourly estimate, multiply the unit rate by the minimum billed allocation and your expected runtime. Storage, data transfer and taxes can add charges. Serverless GPU time may exclude CPU and RAM, while an on-demand machine can be billed for time spent waiting or loading a model. Check the selected plan before deployment.
Model memory and software
Budget memory for weights, KV cache, activations and runtime workspace. Quantization can reduce weight storage, but usable capacity also depends on context length, batch size and the inference engine. Test the intended model and workload rather than treating nominal VRAM as a guarantee that every configuration fits.
Volta is a legacy CUDA architecture. Verify that your selected driver, toolkit and framework still ship compatible kernels before renting. Newer quantization engines and precision formats can require later architectures, so a successful installation on a newer GPU is not enough evidence of V100 compatibility.
Compare V100 SXM3 32GB rental costs
Compare the same model, precision, input length and concurrency across candidate machines. Record end-to-end latency, useful throughput and total job cost, including model loading and supporting resources. This makes the comparison more useful than ranking hardware solely by nominal peak arithmetic.
Browse the GPU explorer for other memory capacities and architectures, or compare GPU cloud providers. The specifications and source links below remain separate from current rental availability, so you can review the hardware even when a provider has no capacity.
Review the official V100 SXM3 32GB hardware reference and the provider’s checkout conditions before deploying a job. Product images are reference views; the exact installed board and host topology depend on the advertised rental configuration.
CHOOSING THIS GPU
Is it right for your workload?
32 GB SXM3 configuration. V100 SXM2, SXM3 and PCIe allocations have separate source identities and rental listings. SXM3 is the provider-reported DGX-2-era V100 form; the image is identified as a V100 module family reference, not an exact host-board inspection.
Best suited to
- Inference and development workloads that fit the recorded memory configuration
- Task-specific benchmarking with the intended model, precision and software
- Comparing hourly rental options for this exact hardware identity
Strengths
- 32 GB recorded nominal memory
- Volta architecture
- Provider-specific pricing and observation timestamps
Things to consider
- Rental availability and included CPU/RAM vary by provider
- Storage, networking and multi-GPU minimums can change the final cost
- Different form factors and partition sizes are separate catalog entries
HARDWARE DETAILS
Inside the GPU
32 GB SXM3 configuration. V100 SXM2, SXM3 and PCIe allocations have separate source identities and rental listings. SXM3 is the provider-reported DGX-2-era V100 form; the image is identified as a V100 module family reference, not an exact host-board inspection.
Image: NVIDIA V100 SXM family reference image, not an exact SXM3 board photograph. This record is the provider-listed SXM3 32 GB configuration.
- Manufacturer
- NVIDIA
- Architecture
- Volta
- VRAM (GB)
- 32
- Memory type
- HBM2
- Form factor
- SXM3
- Memory bandwidth (GB/s)
- Not verified for this edition
- Maximum board power (W)
- Not verified for this edition
- CUDA cores
- Not verified for this edition
- Tensor cores
- First-generation Volta Tensor Cores
- Ray tracing cores
- Not present; Volta compute accelerator
- CUDA capability
- 7.0
- Memory ECC
- Supported; provider and driver settings determine enablement
- Host interface
- Not verified for this edition
- GPU interconnect
- Not verified for this edition
- Hardware partitioning (MIG)
- Not verified for this edition
- Cooling
- Not verified for this edition
Hardware capabilities are not a guarantee of access in a cloud instance. Check the exact edition, GPU allocation and server topology in the rental offer.
MODEL MEMORY
Plan your model size
Weight memory is approximately parameter count × bytes per parameter; allow additional capacity for KV cache, activations and runtime workspace. Nominal VRAM alone does not establish that a model fits. MIG capacity is the allocation size, not total parent GPU memory.
| Example model class | Weight format | Raw weights ≈ | Minimum GPUs for weights only |
|---|---|---|---|
| Llama 3.1 8B ↗ | 4-bit | 4 GB | 1Runtime needs more memory |
| Llama 3.1 8B ↗ | FP16 | 16 GB | 1Runtime needs more memory |
| Qwen2.5 14B ↗ | 4-bit | 7 GB | 1Runtime needs more memory |
| Qwen2.5 32B ↗ | 4-bit | 16 GB | 1Runtime needs more memory |
| Llama 3.1 70B ↗ | 4-bit | 35 GB | 2Runtime needs more memory |
| Llama 3.1 70B ↗ | 8-bit | 70 GB | 3Runtime needs more memory |
| Llama 3.1 70B ↗ | FP16 | 140 GB | 5Runtime needs more memory |
Arithmetic lower bound: rounded parameter count × bits per weight ÷ 8, in decimal GB. Excludes quantization metadata, KV cache, activations, CUDA workspaces and training states. Actual model sizes differ from their rounded names. No context length, batch size or concurrency is guaranteed. GPU counts assume supported model sharding and can be higher in practice. Quantized checkpoints and compatible kernels are required for 4-bit/8-bit execution.
SOFTWARE & PERFORMANCE
Before you deploy
Software compatibility
Use a compatible NVIDIA driver and CUDA-enabled framework/container. Validate the exact architecture, precision and inference-engine kernels before deployment. Volta and MIG partitions can have different support constraints from a full current-generation GPU.
Measured benchmarks
A reproducible, comparable application benchmark has not yet been recorded for this edition. Peak TFLOPS above are not measured tokens per second or image-generation speed.
Compare tests using the same model, precision, GPU count, engine version, input/output length and batch or concurrency. A provider’s server configuration can change the result.
COMPARE YOUR OPTIONS
Alternatives to consider
BUDGET YOUR RUN
GPU cost estimator
An eligible hourly price is not recorded. Check the rental terms below for quotes or reserved commitments.
