Skip to content
Ashlane

Field notes

Short writing from the engineers who run the network and the people who help studios ship on it.

in Platform engineering

What 11.4 Tbps looks like from the origin side

On 19 March, Hollowmere launched, and the edge sent 11.4 Tbps at the peak five-minute window. The interesting number from that day is on the other side of the network: the studio's origin saw 1.9 Gbps at its highest, and 94 GB in total.

That is the work a tiered cache does. A chunk that no edge holds is requested once per regional shield, and every other site in the region fills from the shield. In Europe, 9 sites asked for the same 291,000 chunks and the origin saw each chunk three times, not nine.

We pre-warmed the shields two hours before the embargo lifted, which turned the first-minute cache hit ratio from 61% to 97%. The lesson we pass on to every studio: warm the cache, but warm the shield first.

in Release engineering

Why your day-one patch should never be a full download

Studios still ship a day-one patch as a replacement build, because it is the one thing that is certain to work. The bill for that certainty is easy to compute: 38 GB multiplied by every player who bought the game before launch.

The alternative is to treat the pre-load build as release 0.9.9 and the launch build as 1.0.0, and let delta patching do the rest. In the six launches we measured this year, the median day-one patch was 1.7 GB, or 4.5% of the full build. The players who pre-loaded were playing within a minute of the unlock.

The catch is discipline about what changes between the two builds. If your pipeline re-exports every texture on a nightly job, the patch will be big, and no delta engine can fix that.

in Studio guide

A launch-week checklist for small studios

We have watched about two hundred launches. The ones that went quietly shared a short list of habits, and none of them is expensive.

  • Rehearse. A 30-minute replay of last year's best traffic shape finds the same problems as the real day.
  • Pick a rollback version before you ship, and test that rolling back works.
  • Put a person on the dashboard who is not also fixing bugs.
  • Set the guardrail threshold lower than feels natural. A false pause costs ten minutes; a missed one costs a night.
  • Tell your community the download size before they start. It is the most honest way to avoid support tickets.