GLM 5.1 vs Claude 4.6 Opus

Cursor's Composer is built on Kimi K2.5, which is Moonshot's Chinese model. Shopify switched to Alibaba's Qwen and saved $5 million a year. Airbnb CEO Brian Chesky has said publicly: "We rely a lot on Qwen. It's very good, fast, and cheap." Cognition's SWE-1.6 model is likely post-trained on Zhipu's GLM. And last week Zhipu dropped GLM-5.1, an open source model that benchmarks close to Claude Opus on coding tasks.

Meanwhile the tech press is full of stories about OpenAI vs. Anthropic vs. Google. The narrative is still that American closed-lab models are the ones actually deployed in production. But what's running inside some of Silicon Valley's biggest products right now? Chinese open source.

These companies aren't making ideological choices. They're using Kimi and Qwen because they're fast, cheap, and accurate enough for their specific tasks. That's actually the most interesting part - it's a story about how well-optimized open source competes with frontier labs on real-world economics, not benchmarks. And it's happening faster than most people expected.

There's also a dimension that nobody wants to say out loud: users booking Airbnb trips are getting results from a model built in Shanghai. People using Cursor are getting code completions from a Chinese company's research. Most of them have no idea, and Airbnb didn't exactly put it in the changelog.

The question I'm genuinely uncertain about: does the model's origin actually matter once it's running in your infrastructure, if the data pipeline is controlled by the American company? Or does there remain some structural difference - in training data provenance, in post-training alignment choices, in the incentives of the organization that built it - that carries forward even when the weights are open source?

Build is done. 16 DGX Sparks on the fabric, all hitting line rate.

Setup was time consuming but honestly smoother than I expected. Each Spark runs Nvidia’s flavor of Ubuntu out of the box with mostly everything pre installed and ready to go. For setup I had to rack them, power on, create the same user/pass across all nodes, wait about 20 minutes per node for updates, then configure passwordless SSH, jumbo frames, IPs, etc. which I scripted to save time.

Each Spark connects to the FS N8510 switch with a single QSFP56 cable. The DGX Spark bonds its two NIC interfaces into each port, so you get dual rail over one cable. I'm seeing 100 to 111 Gbps per rail, which aggregates to the advertised 200 Gbps.

**Why this over H100s or a GB300?**

Unified memory. The whole point is maximizing unified memory capacity within the Nvidia ecosystem. With 8 nodes I was serving GLM-5.1-NVFP4 (434GB) at TP=8. Now going to test with DeepSeek and Kimi

The longer term plan is a prefill/decode split. The Spark cluster handles prefill (massive parallel throughput), and once the M5 Ultra Mac Studios drop I'll add 2 to 4 into the rack for decode.

—

Full rack, top to bottom:

\- 1U Brush Panel

\- OPNSense Firewall

\- Mikrotik 10Gb switch (internet uplink)

\- Mikrotik 100Gb switch (HPC to NAS)

\- 1U Brush Panel

\- QNAP 374TB all U.2 NAS

\- Management Server

\- Dual 4090 Workstation

\- Backup Dual 4090 Workstation (identical specs)

\- FS 200Gbps QSFP56 Fabric Switch (Spark cluster)

\- 1U Brush Panel

\- 8x DGX Spark Shelf One

\- 8x DGX Spark Shelf Two

\- 2U Spacer Panel

\- SuperMicro 4x H100 NVL Station

\- GH200