AI Infra Interviews logo
NVIDIA · GPU · reviewed 2026-09-12

NVIDIA L40S

A 48 GB server card for inference, fine-tuning and graphics. The extra capacity is useful; it does not bring an HGX interconnect.

Memory per accelerator
48 GB

GDDR6

Memory bandwidth
0.86 TB/s

Published peak, not measured application throughput

Remember this

L40, L40S and RTX 6000 Ada are distinct products. NVIDIA’s current L40S table lists a dense BF16 value inconsistent with half its sparse value; this reference does not silently choose a peak for that row.

When this is a sensible choice

Start here if…

Use L40S when a supported quantized model or adapter-tuning workload fits in 48 GB. A nominal 70B at four bits has a 35 GB raw weight floor, so a single card is a sizing candidate, not a guarantee.

Choose another configuration if…

For frequent tensor-parallel collectives, compare an NVLink-connected system. PCIe transfers, host topology and quantization kernels can erase the apparent saving of several cheaper cards.

Specifications with their boundaries attached

Architecture
Ada Lovelace
Memory
48 GB GDDR6
Memory bandwidth
0.86 TB/s per accelerator
Peak compute
733 TFLOPS dense FP8; BF16/FP16 vendor table has a rounding inconsistency
Scale-up interconnect
PCIe only; no NVLink
Host attachment
PCIe 4.0 x16
Power
350 W
Partitioning
No MIG
Catalogue status
Documented product

Compute figures are theoretical peaks at the stated precision. Dense and structured-sparse rates must not be mixed. Bandwidth labelled bidirectional combines both directions. See the source documents.

Follow the bytes · conceptual topology

Three bandwidths, three different jobs

Local memory48 GB GDDR6
Compute enginesExecute kernels on these bytes
① Memory bandwidth: 0.86 TB/s
Accelerator AOwn local memory
Accelerator BOwn local memory
Scale-up: NVLink, Infinity Fabric or PCIe
PCIe only; no NVLink
Server AAccelerators + host
Server BAnother fabric domain
③ Scale-out: NICs + switches + placement
InfiniBand, RoCE, EFA or provider-specific transport
A 400 Gb/s NIC has a 50 GB/s raw line-rate equivalent before overhead. A 900 GB/s bidirectional NVLink figure counts traffic in both directions. Neither is the bandwidth at which a GPU reads its own HBM. This diagram explains the boundaries; it is not a wiring diagram for a particular cloud machine.

Where it appears in provider documentation

Documented configurations, checked September 12, 2026. Listing does not guarantee regional stock, quota, allocation size or an on-demand purchase.
Provider / machineNetwork scopeWhat changes the decision
AWS
G4dn / G5 / G6 / G6e
Depends on VM size; no NVLink assumptionRespectively T4, A10G, L4 and L40S. A10G is AWS’s A10-family device. Fractional and full GPU offerings are different products.
CoreWeave
US East region catalogue
InfiniBand appears on designated instance typesThe regional catalogue identifies which configurations carry InfiniBand. Availability and reservations remain zone-specific.

Model fit and software support

These publisher or serving-engine documents mention this hardware family. They have not been reproduced on our machines.

No model-specific recipe in our reviewed set certifies this exact hardware. The memory calculator can narrow candidates, but it cannot establish software support. Read the model register.

What is the memory floor?

Start with total parameters, then add the memory the workload needs. This arithmetic does not certify a serving configuration. All output sizes below are decimal GB.

Override device capacity with the memory exposed by your allocation, particularly for cloud B300 and partitioned devices. The starting 32 GB budget and 15% reserve are editable teaching assumptions. They are not measurements for the selected model. Mixed-precision tensors, quantization scales, vision encoders and draft models can increase the weight payload.

320 GB

Raw weights only
320B × 8 bits ÷ 8

40.8 GB

Budget per device
48 GB × (1 − 15%)

9 devices

Arithmetic lower bound
round up ((weights + 32) ÷ budget)

WeightsCache + runtimeRemaining budget

This assumes perfectly balanced sharding. A result of three does not prove that a three-device parallel layout is supported. Check layer/expert divisibility, actual allocatable memory, precision kernels and the fabric before renting.

320B is the model card’s total; 18B active is not its storage size. The vLLM recipe reports about 306 GiB for the native FP8 checkpoint. Hopper requires BF16 KV for this model; the documented ROCm path targets gfx950, not every Instinct GPU. Read the model source ↗

For full training, also budget gradients, optimizer states, activations and communication buffers. The inference weight estimate above is insufficient.

Tokens per second, TTFT and TPOT are not certified for this hardware in our reference. Use the benchmark checklist to compare an exact model, software revision and workload.

Nearby memory capacities, different tradeoffs

These are comparison candidates selected by memory capacity, not performance rankings or drop-in replacements.

NVIDIA A100 40 GB SXM

40 GB · 1.56 TB/s

40 GB of HBM on the SXM4 form factor. A100 remains useful for BF16 training and supported inference, but cannot execute Hopper’s native FP8 Tensor Core path.

NVIDIA A10

24 GB · 0.6 TB/s

A 24 GB graphics-capable server GPU. It offers more memory than T4, without the HBM or switched links of A100.

NVIDIA L4

24 GB · 0.3 TB/s

A low-power 24 GB inference and media GPU. More compute does not imply more memory bandwidth: its published 300 GB/s is below A10.

Sources and review scope

Manufacturer and cloud documentation checked 2026-09-12. We reviewed specifications and the stated product boundaries; we did not run training or serving benchmarks on this device. Cloud memory and availability can differ by configuration.

  1. NVIDIA L40S specifications · checked 2026-09-12

Cite this reference

AI Infra Interviews. NVIDIA L40S: specifications and workload fit. Reviewed . https://aiinfrainterviews.com/hardware/l40s

Include your access date when citing a changing specification. Link to the specification section for hardware figures or the explanation for a sizing or workload decision.

Research method and limits

We compile manufacturer specifications, cloud documentation, model cards and serving recipes. The reference preserves source units and distinguishes individual devices from nodes and racks. Conflicting figures and unknown fields remain labelled.

Our contribution is the comparison, unit reconciliation, worked arithmetic and workload explanation. Published peaks are vendor specifications. Calculator results are estimates under the displayed assumptions. Neither is a measurement from our own accelerator lab.

For a manufacturer’s specification, consult the original source documents. Cite our page when using its analysis, and retain primary-source attribution for underlying figures. This curated reference does not establish market share, live availability or a universal performance ranking.

Found a discrepancy? Send a correction with the page URL, exact variant, disputed figure and supporting primary document.