llama.cpp b12079 adds a cross-node NCCL path for tensor parallelism
The new build connects cross-process collectives to CUDA and RPC. The merge and release are new; older upstream measurements are not fresh independent results or a promise for arbitrary networked PCs.
llama.cpp released b12079 within this reporting window, incorporating NCCL support for multi-node tensor parallelism. PR #28967 merged on November 3 and the build was published at 21:58 UTC that day. This confirms a newly shipped communication implementation, not an independent multi-machine reproduction by AraoAI or a new hardware launch.
-
Scope. The PR adds a backend interface for collectives across ranks in separate processes, implements it with NCCL in the CUDA backend, and uses it in the RPC server when available. It builds on earlier multi-node work. Release notes also include a DGX Spark-specific communication configuration adjustment. Support for NCCL must not be generalized to every backend or device combination.
-
Deployment relevance. Splitting a model across machines adds communication cost as well as weight capacity. Tensor parallelism depends on exchanging data, so the devices, network and actual selected backend matter. Existing CUDA multi-node deployments have a reason to run a controlled comparison; single-GPU users should not expect automatic acceleration from this announcement.
-
Evidence limits. The associated PR was opened earlier and retains its author's DGX Spark comparison tables. Merging code today does not make those older tables newly measured results. We do not reproduce their throughput figures or label them independent cross-machine validation. This review establishes no matched-workload conclusion for home Ethernet, heterogeneous PCs or other backends.
Keep the previous build and full launch configuration. Fix model, quantization, context, node count and network, then compare prefill, generation and failures while checking the actual communication path. Discoverable machines are not proof of useful scaling: computation and exchange must deliver a benefit together under the same workload. The feature has shipped; its benefit for your deployment still needs verification.
Sources: b12079 release; PR #28967.