Hacker News Reader

Comment by viraptor | Hacker News Reader

I know they don't have to share the details, but the "patched" part is not really clear. Did they update to a new image / more recent kernel / anything else? Much like the redis post linked in HN before, we don't know if the impact is because of the "pti turned off/on" change, or are there more moving parts involved.

View on HN

If I recall correctly from older posts (I played Fortnite for a while), they're using AWS.

That's still not answering many questions. I hope they publish a full analysis at some point.

Since they're using default provisioned EC2 instances, it's likely that the developers don't necessarily even fully understand their performance degradation. They just expect the service that they pay for to work properly.

It's true, but it's not what I meant. They wrote "after a host was patched". This is ambiguous. So they mean the host as in instance, or host as in AWS host machine? Did they just reboot it get on the new/updated VM host, or did they rebuild to include the PTI fixes as well. Did they upgrade anything, or did everything else stay on the same version.

From what I can tell, Amazon isn’t giving people deep technical information. They’ll just send you an email telling you which instances are being forced to restart and when.

Agreed. No detail on what they're running. Ubuntu fixes aren't out yet, so this is early data which is super useful - if we knew what system this is.

Reply on news.ycombinator.com