Post

HighVRAM Weekly Digest #3: A40, L40S, A100 and H100 Server GPU Decisions

This edition: HighVRAM maps the 40GB-to-94GB NVIDIA server-GPU decision across A40, L40S, A100 and H100. The useful question is not which product has the largest peak tensor number. It is which exact card, memory tier, software target and qualified host solve the measured workload without creating a cooling, form-factor or licensing surprise.

Delivery note: this is a web and RSS edition. HighVRAM email signup and delivery are not active, and publication here does not mean an email was sent.

What changed

The new A40 versus A100 comparison keeps the generation broadly constant while separating 48GB GDDR6 ECC from 40GB/80GB HBM, compute capability 8.6 from 8.0, A40 vGPU/display/NVLink behavior from A100 MIG and PCIe/SXM platform choices.

The L40S versus A100 comparison asks whether a newer 48GB Ada inference/media card is more useful than an older HBM accelerator whose 40GB variant actually exposes less capacity.

The L40S versus H100 comparison holds server deployment broadly constant, then isolates the move from 48GB Ada to 80GB/94GB Hopper, MIG and variant-specific NVLink/NVSwitch.

For active workstation installations, the parallel RTX A6000 versus A100 and RTX 6000 Ada versus A100 guides preserve the cooling and display differences instead of treating server accelerators as drop-in desktop cards.

The capacity boundary table

Qwen3.5 artifactFiles40GB48GB A40/L40S80GB A100/H10094GB H100 NVL
35B-A3B Q8 + projector37.802GB2.198GB: unsafe10.198GB42.198GB56.198GB
35B-A3B BF1671.904GBNo file fitNo file fit8.096GB: bounded22.096GB
122B-A10B Q4 + projector77.446GBNo file fitNo file fit2.554GB: unsafe16.554GB
122B-A10B GPTQ-Int478.864GBNo file fitNo file fit1.136GB: unsafe15.136GB
122B FP8 / Q8 + projector / BF16127.163 / 130.781 / 250.173GBNo file fitNo file fitNo file fitNo file fit
File-only decimal-GB arithmetic. KV cache, hybrid state, vision processing, runtime buffers and safety margin are additional. A40 and L40S share the 48GB arithmetic but not architecture or platform behavior; A100 and H100 share nominal 80GB arithmetic but not software generation or system design.

Three traps to avoid

  • More bandwidth with less capacity: A100 40GB publishes more bandwidth than A40 or L40S but leaves only 2.198GB after the listed 35B Q8 files. Bandwidth does not rescue an unsafe memory boundary.
  • “H100” is not one card: PCIe 80GB, SXM 80GB and NVL 94GB require different host, cooling, power and interconnect decisions.
  • Passive does not mean easy: A40, L40S, A100 PCIe and H100 PCIe all need directed server airflow. A bare SXM module is not installable in an ordinary PCIe slot.

One useful action

If you can access two of these systems, run the same model artifact, runtime, precision, context, batch/concurrency and timing boundary, then submit the pair through the benchmark builder. Record exact product/variant, exposed memory, airflow, connector or SXM platform, MIG/NVLink state, placement/offload, prompt and generation metrics, peak device memory and repetitions. The current fixed database has no accepted A40, L40S, A100 or H100 observations.

Continue reading

Sources and limits

Published October 25, 2026. HighVRAM has not independently benchmarked every pair. File fit does not establish compatibility, speed, quality, reliability or value. Specifications and qualified configurations vary by exact SKU.