No items found.
Start Building
Technical

NVLink vs PCIe for AI Workloads: When the Interconnect Is Your Bottleneck

Your model needs NVLink but your budget does not allow CoreWeave's 8-GPU minimum or AWS rates. This guide shows when PCIe works, when it does not, and how to access NVLink from $3.75/hr.

Author photo
packet.ai Team
August 4, 2026

NVLink vs PCIe: NVLink 4.0 on the H100 SXM delivers 900 GB/s of bidirectional GPU-to-GPU bandwidth. PCIe 5.0 x16, the fastest CPU-to-GPU interface available today, tops out at 128 GB/s. That is a 7x gap with a direct cost consequence for solo developers scaling past a single GPU.

Key takeaways

  • NVLink 4.0 (H100/H200) delivers 900 GB/s bidirectional per GPU. PCIe 5.0 x16 delivers 128 GB/s. NVLink is 7x wider.
  • NVLink 5.0 on the B200 doubles that to 1.8 TB/s per GPU, a 14x advantage over PCIe 5.0.
  • PCIe handles single-GPU inference, data-parallel training on 7B-13B models, and 2-GPU setups without issue.
  • Tensor parallelism on 70B+ models triggers AllReduce after every transformer layer. PCIe becomes the hard ceiling.
  • NVLink clusters achieve 92-96% linear scaling. PCIe Gen5 reaches 80-88%. PCIe Gen4 reaches 70-80%.
  • H100 SXM with NVLink 4.0 delivers up to 2.6x faster multi-GPU LLM inference than H100 PCIe variants.
  • packet.ai B200 SXM starts at $3.75/hr, the lowest published on-demand NVLink GPU rate in 2026, 46% below Lambda ($6.99) and 74% below AWS p6 ($14.24). Rent one GPU. No cluster minimum. No contracts.

The NVLink vs PCIe question comes up every time a solo developer, indie hacker, or small team tries to scale past a single GPU. Both are interconnects. Both move data. But they solve different problems at very different speeds, and the wrong choice shows up as GPU utilisation stuck at 60% and training jobs that refuse to scale linearly.

If you are building something cost-sensitive, the good news is that NVLink is no longer gated behind enterprise contracts or 8-GPU minimums. This post covers exactly when you need it, when you do not, and what it costs today.

The Bandwidth Gap: NVLink vs PCIe in Numbers

The fundamental difference between NVLink and PCIe is not architecture, it is bandwidth per GPU. NVLink is a dedicated GPU-to-GPU fabric. PCIe is a general-purpose CPU-to-peripheral bus that happens to connect GPUs.

900 GB/s

NVLink 4.0 per GPU
(H100/H200)

1.8 TB/s

NVLink 5.0 per GPU
(B200)

128 GB/s

PCIe 5.0 x16 max

64 GB/s

PCIe 4.0 x16 max

GPUInterconnectBW / GPUvs PCIe 5.0packet.ai price
A100 80GB SXMNVLink 3.0600 GB/s4.7x$1.43/hr (live)
H100 SXMNVLink 4.0900 GB/s7xLaunching Soon (waitlist)
H200 SXMNVLink 4.0900 GB/s7xLaunching Soon (waitlist)
B200 SXMNVLink 5.01,800 GB/s14x$3.75/hr (live)
PCIe 4.0 GPUPCIe 4.0 x1664 GB/s0.5xN/A
PCIe 5.0 GPUPCIe 5.0 x16128 GB/s1x (baseline)N/A

Source: NVIDIA official datasheets. PCIe per PCI-SIG spec. packet.ai prices verified August 2026. H100 and H200 SXM on waitlist. B200 and A100 available on-demand.

When PCIe Holds Up (and When It Does Not)

Interconnect bandwidth only matters when GPUs are talking to each other. The amount of communication depends entirely on the parallelism strategy your job uses. For most solo developers running models under 70B parameters, PCIe is completely sufficient.

PCIe is sufficient

  • Single-GPU inference or training
  • Data parallelism with 2-4 GPUs
  • 7B-13B models that fit on one card
  • Models using gradient accumulation to reduce sync frequency
  • Pipeline parallelism on sequential model partitions

NVLink required

  • Tensor parallelism on 70B+ models
  • 4-8 GPU clusters where AllReduce runs after every layer
  • Long-context inference with KV cache shared across GPUs
  • Models exceeding the VRAM of a single card at FP16/BF16
  • Latency-critical serving where sync stalls matter
Model SizeExampleParallelism StrategyInterconnect NeededRecommended GPU
7B-13BLlama 3.1 8B, Mistral 7BSingle GPUPCIe fineA100 $1.43/hr (live)
34B-70BLlama 3.1 70B, Qwen 72BTensor Parallel (2-4 GPU)NVLink requiredH200 SXM (waitlist)
405BLlama 3.1 405BTensor Parallel (8 GPU)NVLink requiredB200 $3.75/hr (live)
1T+Frontier / pretraining3D Parallel + InfiniBandNVLink + IBGPU Clusters (quote)

How Tensor Parallelism Exposes the PCIe Limit

In tensor parallelism, a single matrix multiplication is split across multiple GPUs. Each GPU processes its shard of the weight matrix, then every GPU must synchronize results using an AllReduce collective before the next transformer layer begins. This happens after every single layer in the model.

A 70B parameter model running at BF16 has 140 GB of weights and typically 80+ transformer layers. Each AllReduce call moves a volume of data proportional to the activation tensor size across all GPUs simultaneously. On a PCIe cluster, those calls queue behind the shared 128 GB/s ceiling. On an NVLink cluster with NVSwitch, every GPU pair communicates at full 900 GB/s simultaneously, and gradient synchronization across eight GPUs takes roughly the same time regardless of which GPUs are communicating.

NVLink-connected clusters with NVSwitch achieve 92-96% linear scaling for data-parallel training. PCIe Gen5 clusters reach 80-88%, and PCIe Gen4 clusters 70-80%. That gap compounds at every additional GPU added to the cluster.

Pipeline parallelism as a PCIe workaround

If NVLink is unavailable, pipeline parallelism splits the model sequentially across GPUs rather than sharding each layer. This requires far less inter-GPU bandwidth. The tradeoff is pipeline bubbles: idle GPU time between micro-batches. For latency-sensitive workloads, this is a real cost. See packet.ai multi-node GPU cluster training guide for how this changes once you scale beyond a single node.

NVLink C2C (chip-to-chip) is a separate variant of NVLink used to connect a GPU die directly to a CPU die on the same package. The GB200 Grace Blackwell Superchip uses NVLink C2C at 900 GB/s to connect two B200 GPU dies and one Grace CPU in a memory-coherent superchip. This differs from the NVLink 5.0 fabric used for GPU-to-GPU communication between separate GPUs in a cluster.

In a GB200 NVL72 rack, 72 B200 GPUs operate as a single logical unit with 13.5 TB of unified HBM3e memory. The GPU-to-GPU bandwidth via NVLink 5.0 is 1.8 TB/s per GPU, and the full-rack NVLink fabric delivers 130 TB/s aggregate. This makes multi-GPU tensor parallelism for frontier models (405B+ parameters) feasible without pipeline bubbles or PCIe constraints.

The B200's NVLink 5.0 runs at 1.8 TB/s per GPU, doubling the H100's NVLink 4.0 bandwidth, placing the interconnect gap over PCIe 5.0 at approximately 14x. For 8-GPU HGX B200 clusters, total NVLink fabric bandwidth reaches 14.4 TB/s.

For teams renting B200 clusters today, packet.ai B200 SXM is available on-demand from $3.75/hr - NVLink 5.0 fabric included, no waitlist, single GPU access. For a full cost breakdown, see the B200 GPU cloud pricing guide.

NVLink was once gated behind enterprise contracts and 8-GPU cluster minimums. That has changed. For solo developers and small teams, the key variable is not whether you can access NVLink, it is which provider gives you the lowest on-demand hourly rate without a commitment requirement.

ProviderB200 on-demand / GPU-hrMin GPUsContract requiredMonthly (1 GPU, 24/7)
packet.ai$3.751 GPUNone~$2,728
Lambda Labs$6.991 GPUNone~$5,087
RunPod$5.891 GPUNone~$4,285
CoreWeave$8.60+ (8-GPU min)8 GPUsYes (sales process)~$50,000+
AWS p6$14.248 GPUsNo (on-demand)~$10,395

Prices verified August 2026. CoreWeave and AWS require 8-GPU cluster minimums. packet.ai, Lambda, and RunPod offer single-GPU access. Monthly figures assume 24/7 continuous operation at the listed on-demand rate.

packet.ai B200 at $3.75/hr is the lowest published on-demand NVLink rate in 2026, 46% below Lambda, 36% below RunPod, and 74% below AWS p6 for identical silicon. One B200 running continuously costs about $2,728/month on packet.ai versus $10,395/month on AWS. For a breakdown of cost-per-token economics at this price point, see the LLM inference cost guide.

How to Choose: A Practical Decision Framework

Run through these three questions before choosing a GPU configuration. For model-specific VRAM sizing, see the VRAM requirements guide first.

1

Does your model fit on a single GPU at inference precision?

If yes (13B at FP16 fits on a single A100 80 GB), PCIe is fine and the A100 at $1.43/hr is the cost-efficient choice. Interconnect is irrelevant when you are not crossing GPU boundaries. Most solo developer workloads on 7B-13B models stay here.

2

Are you using tensor parallelism or sharding across GPUs?

If yes, you need NVLink. Tensor parallelism (TP) generates AllReduce calls after every transformer layer. On 4+ GPUs running TP, PCIe Gen5 at 128 GB/s becomes the hard ceiling within the first few layers of a 70B model. See how NVLink 4.0 changes the cost equation for multi-GPU workloads.

3

Do you need NVLink access without a contract or cluster minimum?

Most NVLink GPU providers require an 8-GPU cluster (CoreWeave) or a sales engagement. packet.ai lets you rent a single B200 SXM on-demand from $3.75/hr, self-serve, in under 5 minutes. No cluster minimum. No sales call. For solo developers and small teams, this is the fastest and cheapest path to NVLink today.

H100 SXM5 GPUs with NVLink 4.0 deliver up to 2.6x faster LLM inference than H100 PCIe variants in multi-GPU configurations, according to data from GPU cloud providers running equivalent workloads on both form factors.

Availability on packet.ai today

B200 SXM on-demand from $3.75/hr - the only live NVLink GPU on packet.ai, no waitlist, single-GPU access. H100 SXM (Launching Soon) and H200 SXM (Launching Soon) are on the waitlist. A100 80GB is live at $1.43/hr. Not ready to manage GPUs yet? See packet.ai Token Factory for a managed inference API on the same hardware. Join the H100 SXM waitlist here.

If you are a solo developer or small team running 70B+ models with tensor parallelism in PyTorch or vLLM, the SXM form factor with NVLink is the correct choice. On packet.ai today: rent the B200 SXM from $3.75/hr per GPU - no contracts, no cluster minimums, deploy in under 5 minutes.

Frequently asked questions

NVLink is a dedicated GPU-to-GPU interconnect at up to 900 GB/s (H100, NVLink 4.0) or 1.8 TB/s (B200, NVLink 5.0) per GPU. PCIe is a general-purpose CPU-to-peripheral bus maxing at 128 GB/s on Gen5 x16. For multi-GPU AI workloads using tensor parallelism or large AllReduce operations, NVLink removes a bottleneck PCIe cannot overcome at its rated bandwidth.
packet.ai offers the lowest published on-demand NVLink GPU rate in 2026: B200 SXM at $3.75/hr, compared to Lambda at $6.99/hr, RunPod at $5.89/hr, and AWS p6 at $14.24/hr. There is no cluster minimum and no contract. You can rent a single GPU self-serve in under 5 minutes. H100 SXM (Launching Soon) and H200 SXM (Launching Soon) are currently on the waitlist.
Yes, but only for specific parallelism strategies. Data parallelism with infrequent gradient syncs on 2-4 GPUs stays within PCIe's 128 GB/s envelope. Tensor parallelism on 70B+ models generates AllReduce calls after every transformer layer, saturating PCIe quickly and causing GPU idle time. NVLink's 900 GB/s (or 1.8 TB/s on B200) absorbs that traffic without stalling compute.
Yes. Pipeline parallelism splits the model sequentially across GPUs and requires far less inter-GPU bandwidth than tensor parallelism. PCIe Gen5 handles this without saturation. The tradeoff is pipeline bubbles: idle GPU cycles between micro-batches. For throughput-focused batch training where latency is less critical, this is an acceptable tradeoff.
The B200 SXM uses NVLink 5.0 at 1.8 TB/s per GPU for GPU-to-GPU communication and PCIe 6.0 for CPU-to-GPU communication. In the GB200 Grace Blackwell Superchip, a separate NVLink C2C link at 900 GB/s connects the B200 GPU dies to the Grace CPU die with memory coherency. These are three distinct interconnects serving three different communication paths.
For LLM training using tensor parallelism, yes. NVLink 4.0 provides 900 GB/s per GPU versus 128 GB/s for PCIe 5.0, a 7x bandwidth advantage. H100 SXM clusters achieve 92-96% linear scaling compared to 70-80% for PCIe Gen4 clusters. For single-GPU training or data-parallel training with infrequent communication, the interconnect is not the bottleneck.
Bandwidth requirements scale with model hidden dimension and sequence length. For a 70B model at BF16 with hidden size 8192 and 80 layers, each AllReduce moves roughly 8,192 x 2 bytes per token per layer across all GPUs. At batch size 32 and sequence length 2048, aggregate inter-GPU traffic per step exceeds PCIe 5.0 x16 capacity without stalling compute. NVLink 4.0 at 900 GB/s absorbs this in the same time the GPU processes the layer.

Last reviewed: 2026-08-03. Prices verified against packet.ai live product pages. B200 SXM on-demand from $3.75/hr - no contracts, 1 GPU minimum, deploy in 5 minutes. H100 SXM and H200 SXM on waitlist. See full pricing page for all GPU tiers.

Waste less compute.

Same models. Same API. Fraction of the cost. Start free — no credit card required.

Start Building →

More from the blog