Thanks for the feedback, everyone! I plan to wind down the infrastructure over the weekend; I'll bring the servers back up once the IFDB bits are in place.
tomasb wrote:
From central Europe the typical timings of each HTTP request is as follows (please note that typical game turn consists of 4 requests so you must multiply by 4 to get an actual response time)
Great data point, thanks! I wasn't aware of the 4x multiplier. That certainly explains why it's so sensitive to latency.
Europe would really benefit from a more centrally located server. I have this running through Amazon's AWS infrastructure and unfortunately their only EU endpoint is in Ireland.
George wrote:
Averaging about two seconds, so decent. It felt a lot better than when Nikos had his test server in Greece.
That experience was the motivation for this project. Given the latency factor it's better to have a lot of local servers rather than one or two central ones. But it's also important to have a single URL that authors can use to publish their content. tads.io is meant to address both concerns.
It's distinct from IFDB because not everyone will want the game's IFDB page to be the jumping off point for new players. The tads.io game servers will be linked into the IFDB network, and players that come via IFDB will be able to take advantage of the session-sharing and file storage features, but it's entirely optional.
Jim Aikin wrote:
Reasonably responsive with my default server, which I guess is na-west. Output arrives in 1 second or so.
1 second is more or less my standard for acceptable performance. Ideally it would be under 250 ms but that's a hard target to hit without more edge servers.
I get near-local speeds from Seattle to the data center in Oregon, around 250 miles away (400 km). A rough guideline is that you see about 1s of UI lag for every 1000 miles between you and the server. (Like any good rule of thumb, this ignores virtually every technical factor involved.)
Emerald wrote:
Can't speak for Australia as a whole, but here in WA ap-west is definitely more responsive than ap-east. ap-west has about a second of lag, ap-east more like 2 seconds.
Thanks! My guess is that EA would split the difference, so I'll probably go with Singapore until AWS adds an Australian data center.
Laroquod wrote:
NA-East was fastest for me. Unexpectedly, EU-West was nearly as fast (hard to tell the difference) whereas NA-West was a bit noticeably laggy.
That is really surprising and interesting. I wonder how far west into Canada that holds true? Given equal latency, it would be better to divert the traffic to EU-West for load-balancing reasons.