Topology selection
Fat-Tree is versatile and suits most training workloads. Rail-Optimized maps GPUs to network adapters to reduce cross-switch hops.
GPU Cluster Deployment
The delivery scope covers architecture, cabling, system and UFM deployment, NCCL testing of cross-node bandwidth, and at least 24 hours of burn-in. The result is a cluster that has passed acceptance testing and is ready for training at first boot.
Training performance is often limited by cross-node communication. Topology and cabling must be correct at the design stage for measured bandwidth to approach the theoretical value. A single-node test cannot validate this; the full cluster must be tested.
Fat-Tree is versatile and suits most training workloads. Rail-Optimized maps GPUs to network adapters to reduce cross-switch hops.
High-speed Q3400-RA, SN5600, or SN4700 switches; SN2201 management switches; management nodes; enterprise firewalls; and the full set of optical transceivers and cables.
Use a 3D environment during design to simulate routing and calculate each cable length, avoiding shortages or excess material onsite.
Use NCCL across the full cluster to measure cross-node all-reduce bandwidth, compare it with the theoretical value, and issue a report.
A dedicated team manages each stage: finalizing the InfiniBand topology and power and cooling requirements, international logistics and customs clearance, cabling and system deployment, NCCL testing, and at least 24 hours of burn-in. Delivery is complete when the cluster passes acceptance.
Finalize the architecture, InfiniBand topology, rack layout, power and cooling, scalability, and fault-tolerance design.
For overseas projects, manage international logistics and customs clearance. Onsite work covers unloading, racking, 400G/800G cabling, and deployment of the operating system, NVIDIA drivers, and UFM.
Use NCCL bandwidth tests to validate topology and cabling. Run the full cluster at load for at least 24 hours, with the report serving as the acceptance record.
Transfer the burn-in report and topology validation results. Cluster operations begin on the handover date.
Projects span Taiwan, Japan, and Malaysia and include GPU generations from A100 through B300. The largest site in Malaysia is a 100-server-class deployment with 1,024 B300 GPUs. The complete project was handed over after acceptance.
The standard configuration for each B300 server in the cluster: an 8U modular chassis, NVIDIA HGX B300-SXM6 288GB, 6+6 Titanium power supplies, and 8×OSFP 800G high-speed ports.
| Item | Specification |
|---|---|
| Chassis | 8U modular, 6+6 3000W (240V) Titanium power supplies |
| GPU | NVIDIA HGX B300-SXM6 288GB |
| CPU | Intel 6767P, 64 cores at 2.4GHz, 336MB cache, 350W ×2 |
| Memory | 96GB DDR5 RDIMM 6400MHz ×32 |
| System drives | 960GB PCIe Gen4×4 M.2 ×2 |
| Data drives | 3,840GB PCIe Gen4×4 U.2 ×4 |
| Network adapter | NVIDIA BlueField-3 B3240 400G QSFP112 Gen5 dual-port |
| High-speed ports | 8×OSFP 800G |
| Expansion | 4×FHHL PCIe 5.0 ×16, 8×2.5" Gen5 NVMe/SATA |
| Management | BMC AST2600, Intel X710 dual-port 10G |
Do not power on the entire cluster at once. Confirm the compute nodes first, then add high-speed networking, management and monitoring, the network boundary, and the cloud platform one layer at a time. This isolates a fault to the layer being started instead of requiring a system-wide investigation later.
KONST has delivered clusters in Taiwan, Japan, and Malaysia, including a single project with 1,024 B300 GPUs. Clients can contract cluster deployment for an existing data center or combine the data center and cluster under the full compute infrastructure service.
Overseas sites are selected for each project. KONST has delivered sites in Taiwan, Japan, and Malaysia, including one project with 1,024 B300 GPUs.
Yes. KONST can deliver the data center as part of the project. Cluster deployment normally assumes the owner has a compliant facility. If not, KONST first completes the site infrastructure, data center systems, and environmental monitoring, then deploys the cluster.
Yes. The first architecture deliverable defines power per rack, cooling capacity, and rack layout. The MEP system is then designed from those requirements.
Either can supply the equipment. The difference begins after delivery. Manufacturers generally do not handle topology design, cabling, drivers and UFM, bandwidth testing, or burn-in. An integrator remains responsible until the cluster passes acceptance, not merely until the equipment arrives.
Run NCCL bandwidth tests to measure collective communication across nodes, then compare the result with the theoretical bandwidth. This is the primary way to validate topology and cabling.
It must run for at least 24 hours. The contract specifies the actual duration. High-density, liquid-cooled, or large-scale projects may run longer because thermal accumulation and power-limit issues take time to appear.
Yes. The Fukushima project in Japan uses 32 B200 liquid-cooled containers. KONST handled architecture planning, procurement coordination, and acceptance management.
InfiniBand is designed end to end for the LLM training requirements. Switches include Q3400-RA, SN5600, and SN4700. Nodes use NVIDIA BlueField-3 adapters with 400G/800G cabling.
Tell us the training scale and data center conditions. We will respond with a cluster architecture and delivery schedule.