True, but populous though Manhattan is, it hardly warrants its own data center. If latency was their prime concern they would build the data center in the middle of the population density. For North East US, a location between NY and Washington DC would make more sense.
It could be for transatlantic latency, but this would just be between the US and European data centers anyways.
In short, no, I don't think latency would be a big deal here. Correct me if I'm wrong.
When you're Google, 10ms makes a difference. In my own personal experience, a decrease of 100ms in my response time results in a 20% increase of traffic.
Yes 10ms does matter, but building a data center in the middle of NY vs 20 miles outside is not going to create anywhere near 10ms latency, its not even going to create 1ms, on the Google network at least. Your cable provider is a far higher source of latency.
Comments
Latency. Putting things far away from your customers means response time goes up.
True, but populous though Manhattan is, it hardly warrants its own data center. If latency was their prime concern they would build the data center in the middle of the population density. For North East US, a location between NY and Washington DC would make more sense.
It could be for transatlantic latency, but this would just be between the US and European data centers anyways.
In short, no, I don't think latency would be a big deal here. Correct me if I'm wrong.
When you're Google, 10ms makes a difference. In my own personal experience, a decrease of 100ms in my response time results in a 20% increase of traffic.
Latency matters that much.
Yes 10ms does matter, but building a data center in the middle of NY vs 20 miles outside is not going to create anywhere near 10ms latency, its not even going to create 1ms, on the Google network at least. Your cable provider is a far higher source of latency.
Depends on where the Meet-Me centre of the city is - it might even be that building.