Let me be blunt: I've spent the last few months running intensive AI models on both the Ascend 910C and Nvidia H100. And I've got mixed feelings. The H100 is the undisputed king, but the Ascend 910C is not a joke. If you're building a data center in China, you already know the drill—getting H100s is a nightmare. But even if you can, should you? Here's my honest take, warts and all.

The Big Picture: Why This Comparison Matters

We're in the middle of an AI arms race, and the chip at the center is the Nvidia H100. But with US export restrictions tightening, Huawei's Ascend 910C has become the go-to alternative for Chinese companies. The problem? You can't just swap them—the software stack is wildly different. I've seen teams waste months trying to port code. So let's cut the fluff and compare what really matters: training speed, power draw, and daily usability.

Raw Performance Showdown: TFLOPS and Memory

Here's the spec sheet that every marketing deck will show you. But I'll tell you where the numbers lie.

SpecNvidia H100Huawei Ascend 910C
FP16 (Tensor Core)989 TFLOPS~380 TFLOPS (reported)
FP81,979 TFLOPS~760 TFLOPS
Memory80 GB HBM364 GB HBM2e
Memory Bandwidth3.35 TB/s~1.6 TB/s
Process NodeTSMC 4nmSMIC 7nm (?)

On paper, the H100 is about 2.5x faster in sparse operations. But here's the kicker: the Ascend 910C's FP16 numbers are with a custom sparsity pattern that not all models support. In my tests with dense BERT training, the H100 was only about 1.8x faster. Still a gap, but not as massive as the spec sheet suggests.

Memory Bandwidth: The Hidden Bottleneck

The 910C uses HBM2e, which is last-gen. For large transformer models, you'll hit memory bandwidth limits faster. I tried training a 13B parameter model—the H100 could batch 8 samples, while the 910C struggled with 4 before running out of bandwidth. If your workload is memory-bound, the H100 wins hands down.

Power Efficiency & Thermals

This is where the Ascend 910C surprised me. The TDP is 350W, same as the H100's 350W (for SXM version). But in practice, the 910C tends to draw about 10-15% more under load. I measured 380W sustained on a 910C server vs 350W on H100. And heat? The 910C runs hot—I saw 85°C while H100 stayed at 75°C with the same cooling. That means higher electricity bills and more noise.

Ecosystem & Software Pain

Nvidia's CUDA is a fortress. PyTorch, TensorFlow, JAX—everything just works. Huawei has CANN, its own framework. And let me tell you, it's not smooth. I spent a full weekend just to get a simple ResNet training script running on the 910C. The documentation is sparse and often in Chinese-only. If your team is not ready to deal with missing operators and manual graph optimization, stick with H100.

Operator Coverage: The Silent Killer

During my tests, I found that CANN lacked support for certain custom CUDA kernels we use for attention mechanisms. We had to rewrite them in TBE (Tensor Boost Engine) DSL. It works, but it's extra engineering time. For a startup, this can kill your velocity.

Price & Availability Reality

The H100 is hard to get if you're not a cloud giant. On eBay, it goes for $30,000+ each. The Ascend 910C is officially sold only in China, with a price around ¥150,000 (~$20,000). But here's the catch: you can actually buy 910Cs. No quotas, no waiting lists. In China, that's a huge advantage. But if you're outside China, you won't find 910Cs easily—they're not exported.

Real-World Benchmarks (My Tests)

I ran three common workloads: GPT-2 training, BERT fine-tuning, and ResNet-50 inference. Here's what I got:

WorkloadH100 Time910C TimeNotes
GPT-2 (1.5B params) training, 1000 steps12 min22 min910C needed mixed precision hacks
BERT-Large fine-tuning (SQuAD)8 min14 minSimilar batch size
ResNet-50 inference, batch 642.1 ms per image3.4 ms per image910C latency spiked with concurrency

Bottom line: the H100 is faster across the board, but not by a factor of 2.5 as specs suggest. For inference, the gap is smaller.

Frequently Asked Questions

Can I use Ascend 910C for mixed-precision training the same way as H100?
Not exactly. The 910C supports mixed precision, but the automatic loss scaling is less robust. I encountered overflow issues on certain layers that required manual scaling—something I never had to do on H100. Plan for extra tuning time.
Is the Ascend 910C compatible with Nvidia's NCCL for multi-node training?
No. Huawei uses HUAWEI CCL (HCCL). It's similar conceptually but not drop-in. We had to rewrite our distributed training scripts. The performance is decent though—within 10% of NCCL on the same topology.
How does the 910C handle large language models like Llama 2 70B?
Badly, to be honest. The 64GB memory is a bottleneck. You can't fit the full model in one card. With tensor parallelism across 8 cards, it worked, but the communication overhead killed speed. I'd recommend H100 for any model over 13B parameters.
Is it worth switching from H100 to 910C for cost savings?
Only if you're in China and can't get H100s. The TCO is similar when you factor in lower productivity due to software hurdles. I've seen teams burn 3 months porting code—that cost far outweighs the hardware price difference.