Office 365 Network Optimization and Troubleshooting. Jeff Mealiffe Principal Program Manager Microsoft Office 365 Engineering

Office 365 Network Optimization and Troubleshooting Jeff Mealiffe Principal Program Manager Microsoft – Office 365 Engineering Microsoft has invest...
Author: Archibald Casey
2 downloads 0 Views 5MB Size
Office 365 Network Optimization and Troubleshooting Jeff Mealiffe Principal Program Manager Microsoft – Office 365 Engineering

Microsoft has invested $15 billion in infrastructure, building over 100 datacenters and we are constantly evaluating new locations Our high-performing network is one of the top 3 in the world with public peering in 23 countries with 1,500 ISPs. Our Datacenters support over 20 Million businesses and over 200 Online Services. Office 365 is sold in 131 markets, 43 languages, and 25 currencies.

Office 365 DC locations Other Microsoft DC locations

Microsoft has datacenter capacity around the world…and we’re growing

Quincy Cheyenne

Dublin

Chicago Boydton

Amsterdam

Shanghai Hong Kong

Des Moines

San Antonio Singapore

Brazil

35+ factors in site selection:  Proximity to customers  Energy, Fiber Infrastructure  Skilled workforce

Australia

 1+ million servers  100+ datacenters in 40+ countries

Japan

The green circles represent Microsoft Edge nodes live for the Office 365 Portal. There are many other Microsoft edge nodes that are not yet compliant with Office 365.

EDGE

TCP connect SSL connect San Antonio DC

TTFB

Reusing existing connections

Edge reuses connections between to further improve performance

TTLB

Without Edge, entire request over ISP’s network

Content Time EDGE

With Edge, Microsoft’s network brought closer to the user

Client RTT

Server RTT

App Latency



• •

Brisbane

Australia

Kuala Lumpur

Malaysia

Los Angeles

USA

Melbourne

Australia

Amsterdam

Netherlands

Miami

USA

Perth

Australia

Auckland

New Zealand

New York

USA

Sydney

Australia

Wellington

New Zealand

Palo Alto

USA

Vienna

Austria

Moscow

Russia

San Jose

USA

Luxembourg

Luxembourg

Singapore

Singapore

Seattle

USA

Sao Paulo

Brazil

Stockholm

Sweden

Montreal

Canada

Zurich

Switzerland

Toronto

Canada

Taipei

Taiwan

Prague

Czechoslovakia

London

UK

Paris

France

Ashburn

USA

Frankfurt

Germany

Atlanta

USA

Hong Kong

Hong Kong

Boston

USA

Dublin

Ireland

Chicago

USA

Milan

Italy

Dallas

USA

Turin

Italy

Denver

USA

Tokyo

Japan

Honolulu

USA

Seoul

Korea

Las Vegas

USA

• • • • •

Site data is published at http://www.peeringdb.com/view .php?asn=8075 Some cities have multiple peering points Peering locations may be on-net or off-net Peering may involve physical connection and/or routing advertisements Data as of July 2014 is subject to change

Outlook, Outlook Web Access, OneDrive for Business Native clients on tablets, PCs, & desktops

Native clients on mobile devices

Browser-based Clients also cache with HTML5

Browser-based mobile clients

Office 365 offers a wide variety of options across devices for customers to access the service OWA uses HTML 5 Offline Application Caching if enabled in Offline Settings

Server workloads

Microsoft network

Microsoft edge nodes

Internet peering and routing

Content delivery network

Customer Internet connection

Rich client applications

Exchange Online http://aka.ms/tune SharePoint Online • Similar to on-prem HTTPS views of webpages, uploads/downloads of content ••Lync Estimates rely upon on-prem baselines Online Office Web Apps or Office •• Document Cached modeediting reduceswith impact and provides for latency tolerance (