B is correct. HPE Slingshot uses fine-grained adaptive routing to make efficient use of available fabric paths. For traffic that can tolerate reordering, the network can make routing decisions at packet granularity, steering packets away from congested links and distributing high-bandwidth MPI or storage traffic across the fabric. This is particularly useful in HPC environments where compute collectives and Lustre I/O can create dynamic hotspots that are difficult to predict with static routing.
Option A is false because Slingshot is an Ethernet-based HPC interconnect, not InfiniBand NDR. Option C incorrectly characterizes its congestion management as primarily DiffServ-based; Slingshot uses specialized congestion-control and telemetry mechanisms designed for HPC traffic behavior. Option D overstates a topology requirement. HPC applications do not require every fabric to be constructed as a mathematically non-blocking network, and Slingshot’s value includes maintaining performance through adaptive routing and congestion management even under variable traffic.
The design goal is sustained application throughput, not merely peak link speed. Efficient path use keeps compute nodes from idling behind network congestion.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit