SharkTech Denver Data Center: Real-World Testing of 1Gbps Bandwidth Server Performance

Looking for an honest take on SharkTech's Denver server performance? Based on actual testing data, this evaluation covers everything from hardware specs to network routing—showing you exactly what to expect when deploying in this location. You'll see real bandwidth numbers, latency measurements across different carriers, and routing patterns that matter for your specific use case.

What We Tested: The Hardware Setup

The test machine ran dual E5-2680v3 processors at 2.5GHz—that's 24 cores with 48 threads total. Memory clocked in at 64GB, paired with 2TB HDD storage. With BBR enabled, the average I/O hit 134MB/s in standard tests.

When we dug into the FIO benchmarks, the storage performance showed its true colors. These numbers paint a clearer picture than basic disk speed tests—you're looking at consistent read/write performance that holds up under load.

Bandwidth Reality Check

Evening tests revealed upload speeds maxing out around 445Mbit/s, with downloads reaching 818Mbit/s. Not quite the full gigabit, but that's typical for real-world conditions outside peak hours.

The iperf3 results for transatlantic traffic looked solid. European and North American endpoints showed respectable throughput—nothing spectacular, but workable for most deployment scenarios.

How It Connects to China

Here's where things get interesting. The routing patterns tell you everything about what kind of performance you'll actually see.

Going into Denver from China:

China Telecom routes through backbone networks, taking a detour through European Telia before landing in North America. It's the long way around, and you'll feel it in latency.

China Unicom sticks to the 169 backbone—more direct, generally more predictable.

China Mobile uses CMI through Hong Kong, then jumps to Telia. Another indirect path that adds hops.

Coming back to China from Denver:

For Telecom users, Guangzhou and Beijing traffic hits the 163 network, while Shanghai gets a direct connection. That Shanghai route is the winner here.

Unicom traffic goes through Comcast—straightforward enough, though not optimized for speed.

Mobile traffic bounces through either Telia or Cogentco. Both work, neither is particularly fast.

If you're running services that need consistent, low-latency connections to mainland China, this isn't your ideal setup. Denver wasn't built with direct China peering in mind. 👉 For deployments targeting Asian markets, check out SharkTech's Los Angeles location instead—it's specifically optimized for trans-Pacific routing.

Benchmark Scores

The Unixbench results showed single-core performance only—not the full multi-core numbers you might expect. That's more about the testing conditions than the hardware capability, but worth noting if you're comparing specs.

Domestic ping tests from various Chinese cities showed the expected pattern: coastal cities performed better than inland locations, with average response times reflecting that indirect routing we saw in the traceroutes.

The Bottom Line

SharkTech's Denver facility delivers exactly what you'd expect from a mid-America data center: solid hardware, decent bandwidth, and routing that prioritizes North American and European connectivity over Asian markets. The 60Gbps DDoS protection comes standard, which matters if you're running anything public-facing.

For projects focused on North American users, this location makes sense. The hardware performs well, the network holds up under testing, and you're getting genuine enterprise-grade infrastructure. But if your users are primarily in Asia, the routing paths work against you—those detours through Europe and multiple backbone hops add up fast. When network topology matters for your deployment, choosing a data center with optimized routes to your target audience isn't just about speed—it's about consistent, reliable performance that your users will actually notice. 👉 Explore SharkTech's full data center options to find the location that matches your routing needs.