Skip to content

devlog

What the analytics were spending

2026-10-25

The analytics allowance ran out during the surge. Most of it had gone on noise, so the next build sends a sample and each repeat once.

I wrote in passing that I went blind when the analytics allowance ran out. This is what had used it.

Over 732,000 frame-rate samples and 286,000 hang reports, from every session. A view event counted more than three times per visitor. One error repeated 17,000 times by 27 people. A key held down, sending a camera change on every auto-repeat. Almost none of it was a decision I could make from.

So performance events now come from a 5% sample of page loads, with the sample rate attached so the numbers can be scaled back up. A repeated error reports at the 1st, 10th, 100th, 1,000th and 10,000th time, and each page load can report 20 at most. View events fire once. A camera change is only sent for the view you settle on.

A related one: when a graphics device dies, Chrome names it in brackets, and my check for that message did not match the brackets. So every error after a device loss looked like a fresh crash. Fixing the string removed a false alarm that had been counted for 289 people.

The Settings opt-out works exactly as before.