Why Hytale Treasure Hunt Servers Throttle at 100 Players (And How We Fixed It)

The Problem We Were Actually Solving

Our public alpha weekend attracted 4,200 concurrent players across three regions, but any region crossing 100 players saw latency spike to 1.4 s per treasure packet and packet loss hit 22 %. Players reported chests teleporting or duplicating; our ReplayCraft logs showed duplicate LootGenerated events exactly when the Go runtimes GC paused hit 120 ms. The Hytale client expects deterministic state updates every 50 ms; at 108 ms we breached the contract. The logs contained 43,000 lines of runtime: out of memory: cannot allocate 16384-byte stack every 47 seconds, triggered by the arena engine spawning a per-player sync.Pool of 64 KB buffers.

What We Tried First (And Why It Failed)

We rewrote the treasure tracker in Go 1.21 with two optimizations:

1. Replaced the mutex-protected map[int64]TreasureState with a sharded hash (256 slices), which dropped P99 latency from 1.4 s to 380 ms.


2. Added a per-player ring buffer to eliminate GC during hot paths.

The sharding gave us a 3.7× throughput bump, but now the bottleneck moved to the arena scheduler. Each players coroutine still wrote to a buffered channel that the main event loop drained once per tick. At 100 players the channel filled in 2.3 ms and the scheduler yielded, but the GC phase added another 110 ms of stop-the-world because we had 3.2 million in-flight allocations from the coroutine stacks. The pprof heap profile showed 1.4 GB live at the inflection point; we capped at 512 MB before swapping began. We tried GOMEMLIMIT=512MiB, but the scheduler kept preempting goroutines to scan stacks, so the tick budget slipped to 89 ms and chest flicker returned.

We benchmarked with wrk2 at 120 RPS and watched p99 climb again to 850 ms. The Go scheduler simply cannot context-switch 1,200 green threads in 50 ms without pausing the world.

The Architecture Decision

I pulled the trigger on a rewrite in Rust with Tokio 1.25 and dashmap for the sharded treasure table. The decision was not about raw speed; it was about latency tail and GC determinism.

Key trade-offs:

• Rust forced us to model the treasure table as an Arc<DashMap<u64, TreasureState>> locked per-shard; we gained zero-cost abstraction safety but had to abandon Gos dynamic stack growth.


• Tokios work-stealing scheduler replaced Gos M:N model; we switched from 1,200 green threads to 4 worker threads pinned to cores 2-5, with the rest dedicated to Hytales packet I/O.


• We replaced the per-player ring buffer with a mpsc channel configured with buffer = 0 so senders block if the receiver lags. This eliminated the GC pause spike because the receiver only allocates when it can keep up.

The first build leaked TreasureState inside an Arc, causing 4 MB/sec of allocations. valgrind --leak-check=full pointed to an Arc::downgrade that should have been Arc::clone. After fixing, jemalloc reported 312 KB/sec allocation at steady state versus the Go builds 4.8 MB/sec.

What The Numbers Said After

We redeployed to the same 8×32-core box running Ubuntu 22.04 with kernel 5.15 and measured again with perf and wrk2.

Latency distribution at 120 RPS:

p50 18 ms

p95 30 ms

p99 46 ms

packet loss 0.06 %

Heap profile at 120 RPS showed 89 live allocations, total 47 KB. Tokios work-stealing scheduler never blocked longer than 1.2 ms during the 50 ms tick. The GC phase (actually Tokios cooperative task cleanup) added 0.8 ms to the worst tick, versus the Go builds 110 ms.

CPU usage at 180 RPS peaked at 42 % user, 18 % system, versus the Go builds 98 % user after 100 players. The Rust build handled 220 RPS before saturation; the Go build collapsed at 130 RPS.

What I Would Do Differently

I would not have wasted three weeks on Go sharding experiments. The coroutine model is a productivity trap when the runtimes scheduler cannot respect a 50 ms budget. I would insist on profiling the scheduler pre-production. If the language runtime cannot allocate green threads without occasional 100 ms pauses, do not build the game state layer on it.

We also over-allocated channels. Tokios mpsc with a zero-length buffer is a latency hand grenade; we should have started with a depth of 16 and bounded the receiver to drop packets if the treasure engine lags. That would have exposed the head-of-line blocking earlier.

The Rust rewrite cost us 4 engineer-weeks of debugging borrow-checker lifetime errors and async-trait quirks, but it delivered a service that scales predictably past 200 players without resorting to zone partitioning. The language was the constraint; once we changed it, the system