Sep 06 2016 05:42 AM
Hi,
I'm wondering how Microsoft decides to distribute the data between all of their data centers.
Reason why I'm asking this is because we are an international company with over 5500 mailboxes and sites all of the world.
However, all of our mailboxes are located in datacenters in Europe:
We have, for instance, a lot of users in Singapore, India, South America, Australia, etc...
I imagine that the performance would be much better if the mailbox is actually stored in the region the user resides in.
On This page you can find all the data centers.
I've used This script to determine the Exchange Online mailbox locations in our environment.
Thanks for your input.
Sep 06 2016 12:09 PM
SolutionSep 06 2016 10:21 PM
Hi Steven true, but there will be some latency in a different part of the world. I guess you would need to ask MS if they can replicate your tenant over more continents.
Sep 06 2016 11:11 PM
Sep 07 2016 09:32 AM
Sep 10 2016 09:33 AM - edited Sep 10 2016 09:36 AM
I agree that Microsoft has a very strong peering around the world hence it should take no more than a couple of hops before entering their backbone network. However, even Microsoft cannot overcome the laws of physics and the speed of light. If you take the direct distance between Singapore and Amsterdam, it's about 10,500km which would take about 35ms for light to travel in a vacuum or about 70ms round-trip. In reality though, it's unlikely that the round-trip latency would fall below 150-160ms at best.
I also agree that some contents are pushed out to the edge via CDN. For example, those icons that appear in the browser when using OWA are delivered via the CDN. Yet, almost nothing comes from the CDN when using the Outlook client. On top of this, the protocol used by Outlook to connect to Exchange Online is either MAPI/HTTP or Outlook Anywhere and both protocols are more sensitive to latency than standard HTTP(S) that OWA uses. Finally, while it's true that cache mode helps with the sending/receiving emails, not everything within Outlook uses cache mode. For example, access to Online Archive does not use cache mode hence latency affects performance. It's a known issue that large Shared Mailbox doesn't work well in cache mode and latency also comes into play here.
Just to give you an idea, sending a 10MB attachment on a LAN took 9s while it took 58s with a WAN latency of 60ms.
Going back to Aldin's comment about performance improvement in moving the mailboxes to their regions - yes, this is definitely true but this isn't something that's currently available for the majority of the O365 customers. I've worked with large customers who are O365-Dedicated customers and it's indeed possible to move the mailboxes closer to the users. However, there is also a downside to this in terms of data sovereignty and what happens when the user travels around the world.
Last of all, the company that I work for, Riverbed Technology, has a solution known as SteelHead SaaS that can ensure the user's performance regardless of where they are in the world. Feel free to reach out to me if you're interested in learning more about this solution.
Thanks,
Blanco
Sep 10 2016 01:25 PM
Sep 12 2016 08:36 PM
There's a really good description of Office 365 client connectivity here
Sep 06 2016 12:09 PM
Solution