Hacker Newsnew | past | comments | ask | show | jobs | submit | evanosaurus's commentslogin

These three things (plus your addendum of working together to solve stupidly hard problems) are basically why I love going to work every day.

(I work at Epic on Team Online, aka the team that this whole PM is about.)


Glad to hear you're loving it. And thanks for detailed yet fun write-ups like this. Keep on keeping on!


We’d love to, but have been told that our providers don’t yet have enough capacity for us to flip our entire fleet over to c5’s just yet.


We don’t tick at 30Hz. Somewhat slower than that. Working on making that better, though.

And we do indeed take advantage of reserved instances. We’re also looking at other options along these lines.


Nope. No creative counting. Those are our real numbers.


I want bandwidth monthly pricing (maybe it adds up)! And what's minimum networking required on each server ?


Hi. Guy who does the autoscaling code here at Epic. It's really fun to watch the graphs of how many server sessions we have in a region at any given time over the course of a day.


I like that you're in here commenting. After reading through the postmortem, it reminds me of scaling issues we had at previous job. We had hundreds of thousands of clients that would get "hyper active" if they had issues connecting, retry loops FTW.

System goes down and it was hard resurrecting it since the traffic just kept pounding away. No autoscaling, no cloud. It woulda been handy to just fire up some more servers, let alone have things auto-scale via CPU %.


We run 16 game servers per c4.8xl instance for Battle Royale. We run more than that (on a different instance type) for StW.


Our account service went down for a brief period this morning. Sorry about that.


This is why we’re mostly stuck in Perforce hell in the games industry.


>Do not show alerts in the Touch Bar, and do not use the Touch Bar for widgets.

It's interesting, then, that they explicitly showed the Touch Bar being used for alerts in the design video (when the user received a FaceTime call).


An incoming call isn't an alert. It's a highly time sensitive notification.

An alert is something that blocks further input until it is dismissed. Something along the lines of "Are you sure you want to disable encryption?" or "This item can not be deleted because it is locked."


I think that it was providing shortcuts for interacting with an alert already displayed on the main screen. Apple's worry, I'm assuming, is that alerts will be displayed only on the bar and people without the new Pro will not notice them.


Do as I say, not as I do?


But was that an alert, or simply presenting the controls necessary to answer the call?


You can't flash the firmware yourself, as the keys are discarded as soon as they're generated per device.

What you could do, however, is read the bits off of the firmware and make sure they're identical to the bits you make from source. Reproducible builds, and all that.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: