You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/frontdoor/troubleshoot-performance-issues.md
+23-21Lines changed: 23 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,15 @@ ms.author: stdoroff
14
14
15
15
# Azure Front Door Performance
16
16
17
-
Performance issues can originate in several potential areas. This guide will assist in identifying which hop along the data-path is most likely the root of the issue and how to resolve. As a brief overview, the issue could be at the Azure Front Door (AFD), the origin, the requesting client or the path between any of these hops.
17
+
Performance issues can originate in several potential areas. This guide in identifying which hop along the data-path is most likely the root of the issue and how to resolve. As a brief overview, the issue could be at the Azure Front Door (AFD), the origin, the requesting client or the path between any of these hops.
18
18
19
19
## Check for Known Issues
20
20
21
21
Before beginning, be sure to check for any [known issues on the AFD platform](https://azure.status.microsoft/status), any known ISPs in the path or on the requesting client's ability to connect and retrieve data.
22
22
23
23
## Scenario 1: Investigate the Origin
24
24
25
-
If one of the origin servers are slow then the first request for an object via the AFD will also be slow. Further, if the content is not being cached at the AFD's Point of Presence (POP), every request will be forwarded to the origin, negating the benefit of the POP's proximity to the requesting client, and relying on the origin's performance.
25
+
If one of the origin servers are slow, then the first request for an object via the AFD is slow. Further, if the content isn't cached at the AFD's Point of Presence (POP), requests are forwarded to the origin. Serving from the origin negates the benefit of the POP's proximity and local delivery to the requesting client, and, instead, rely on the origin's performance.
26
26
27
27
### Scenario 1 | Environment Information Needed
28
28
@@ -40,7 +40,7 @@ If one of the origin servers are slow then the first request for an object via t
40
40
> To check response headers, utilize your browser's Developer Tools (F12), select the *Networking* tab, then the relevant file to be investigated, then the *Headers* tab. ***If the file is missing*** the page need to be reloaded with Developer Tools (F12) open.
41
41
42
42
- The initial response should have an *x-cache* header with *TCP_MISS* value
43
-
- Requests with this value are being forwarded by the AFD's POP to the origin and returning on that same path to the requesting client
43
+
- Requests with this value are forwarded by the AFD's POP to the origin and returning on that same path to the requesting client
44
44
- Examples
45
45
- TCP_MISS
46
46
@@ -99,15 +99,15 @@ If one of the origin servers are slow then the first request for an object via t
99
99
```
100
100
101
101
1. Continue to request against the endpoint until the *x-cache* header has a *TCP_HIT* value
102
-
1. ***If the performance issue is resolved***, then the issue was based on the origin's speed, and is not the of the AFD's performance. The AFD's cache settings or the origin will need to be address by it's owner to resolve the performance issue.
102
+
1. ***If the performance issue is resolved***, then the issue was based on the origin's speed, and isn't the AFD's performance. The AFD's cache settings or the origin need to be address by it's owner to resolve the performance issue.
103
103
1. ***If the issue persists***, then the issue may be with the client requesting the content or the AFD
104
104
A. Move to Scenario 2 to identify
105
105
106
-
## Scenario 2: A Single Client or Location (ie. ISP) is Slow
106
+
## Scenario 2: A Single Client or Location (example: ISP) is Slow
107
107
108
-
This could happen if there is a bad network route between the requesting client and the AFD POP. Any bad route should be ruled out as it will affect the distance to the POP, removing the AFD POP's proximity benefit.
108
+
A single client or location being slow can happen if there's a bad network route between the requesting client and the AFD POP. Any bad route should be ruled out as it affects the distance to the POP, removing the AFD POP's proximity benefit.
109
109
110
-
This could be because of an ISP issue, the customer is using a VPN or they are a part of a corporate network that runs all traffic through a central, remote point.
110
+
High latency, or low bandwidth, could be because of an ISP issue, the customer is using a VPN or they're a part of a dispersed corporate network. A corporate network can run all traffic through a central, remote point.
111
111
112
112
### Scenario 2 | Environment Information Needed
113
113
@@ -130,24 +130,26 @@ This could be because of an ISP issue, the customer is using a VPN or they are a
130
130
```
131
131
132
132
1. Determine if the traffic is taking a path that would add time or travel to a distant region
133
-
- Look for IP, city or country codes that do not take a reasonable route based on the customer’s geography (ie. a customer in Europe getting routed to the United States), or excessive number of hops
133
+
- Look forIP, city or region codes that don't take a reasonable route based on the customer’s geography (example: a customerin Europe getting routed to the United States), or excessive number of hops
134
134
1. Test from a different requesting client in the same region
135
-
1. **If additional hops or remote regions are identified**, the issue will be with the client accessing the AFD POP and not with the AFD itself. This will need to be addressed by the connectivity or VPN provider.
136
-
1. **If additional hops or remote regions are not identified** AND the content is being served from cache (x-cache: TCP_HIT), the issue will likely be with the AFD and a Support Request may need to be created. Include a reference to this troubleshooting article and steps taken.
137
-
- ***Note***: If the content is being served from the origin (x-cache: TCP_MISS), see Scenario 1<insert link when available>
135
+
1. **If additional hops or remote regions are identified**, the issue is with the client accessing the AFD POP and not with the AFD itself. Hops between endpoints needs to be addressed by the connectivity or VPN provider.
136
+
1. **If additional hops or remote regions are not identified** AND the content is being served from cache (x-cache: TCP_HIT), the issue is with the AFD and a Support Request may need to be created. Include a reference to this troubleshooting article and steps taken.
137
+
- ***Note***: , when the content is being served from the origin (x-cache: TCP_MISS), see Scenario 1 above
138
138
139
139
## Scenario 3: A Website Loads Slowly
140
140
141
-
There are some scenarios where there is ***not*** an issue with a single file but the performance of the whole, AFD proxied, webpage is unsatisfactory. This will usually be revealed by a webpage performance tool and will show under performance compared to the webpage outside of AFD.
141
+
There are some scenarios where there is ***not*** an issue with a single file but the performance of the whole, AFD proxied, webpage is unsatisfactory. Site performance is revealed by a webpage performance tool and shows under performance compared to the webpage outside of AFD.
142
142
143
-
A webpage will often consist of many files. The way the AFD offers benefit for the webpage is if each file in the webpage is being served from the origin linked to the AFD and the AFD is configured to optimize the delivery of that file. For example:
143
+
A webpage often consists of many files. The way the website benefits from the AFD is only if each file in the webpage is being served from the AFD. Additionally, the AFD must be configured to maximize the benefit. For example:
144
144
145
145
- Origin: origin.contoso.com
146
146
- AFD Custom Domain: contoso.com
147
147
- Page customer attempts to load: https://contoso.com
148
-
- **Explanation**: When the page loads, the initial file at the "/" directory calls other files which build the page. These are images, javascript, text files and more. If those files are not called via the AFD hostname, *contoso.com*, the AFD will ***not*** be utilized. So, if one of the file requested by the website is *http://www.images.fabrikam.com/businessimage.jpg* the file will ***not*** benefit from the use of the AFD. Instead, the file will be requested directly, from the *images.fabrikam.com* server, by the browser on the requesting client.
148
+
- **Explanation**: When the page loads, the initial file at the "/" directory calls other files, which build the page. These files are images, JavaScript, text files and more. If those files aren't called via the AFD hostname, *contoso.com*, the AFD is ***not*** being utilized. So, if one of the file requested by the website is *http://www.images.fabrikam.com/businessimage.jpg* the file is ***not*** benefiting from the use of the AFD. Instead, the file is being requested directly, from the *images.fabrikam.com* server, by the browser on the requesting client.
149
149
150
-
:::image type="content" source="..." alt-text="Example of multiple, differently sourced files for a singular website and how it affects AFD performance":::
150
+
:::image type="complex" source="media/troubleshoot-performance-issues/AFDCDNPerformance.jpg" alt-text="Example of multiple, differently sourced files for a singular website and how it affects AFD performance":::
151
+
152
+
:::image-end:::
151
153
152
154
### Scenario 3 | Environment Information Needed
153
155
@@ -157,19 +159,19 @@ A webpage will often consist of many files. The way the AFD offers benefit for
157
159
- Origin Hostname
158
160
- Geographical location of the origin
159
161
- Full URL of Affected Webpage
160
-
- Tool and metric which is measuring performance
162
+
- Tool and metric, which is measuring performance
161
163
162
164
### Scenario 3 | Troubleshooting
163
165
164
-
1. Review the metric which is showing the slower performance
166
+
1. Review the metric, which is showing the slower performance
165
167
> [!IMPORTANT]
166
168
> If it is based on a third part tool, Microsoft cannot discern what is being measure by tools not owned by Microsoft
167
169
1. Pull up the AFD webpage in a Browser with Developer Tools (F12) enabled
168
170
> [!NOTE]
169
171
> Developer tools in your browser can be used to determine the source of the files being served
170
172
1. Note the source of files
171
-
1. Identify which files are utilizing the AFD hostname and which are not
172
-
A. Example: From the above example, an AFD hosted image would be something like https://www.contoso.com/productimage1.jpg and that which is not would be something like http://www.images.fabrikam.com/businessimage.jpg
173
+
1. Identify which files are utilizing the AFD hostname and which aren't
174
+
A. Example: From the above example, an AFD hosted image would be something like https://www.contoso.com/productimage1.jpg and that which wouldn't is something like http://www.images.fabrikam.com/businessimage.jpg
173
175
1. Once gathered test performance for file being served from AFD, its origin and, if applicable, the testing webpage
174
176
> [!IMPORTANT]
175
177
> If the origin or testing webpage is served from a geographical region closer to the tool testing performance, a tool or requesting client may need to be used in another region to examine the AFD POP's proximity benefit
@@ -181,7 +183,7 @@ A webpage will often consist of many files. The way the AFD offers benefit for
181
183
> Any files served from outside the AFD's hostname will not be able to benefit from it and the webpage may need to be redesigned to do so
182
184
183
185
1. **If the collected data shows that files are being issued from servers outside the AFD's hostname or performance is better at the AFD**, the AFD is working as expected
184
-
A. This may require a change in webpage design, forassistancein optimizing your website to leverage an AFD, connect with your website design team or our [Microsoft Solution Providers](https://www.microsoft.com/solution-providers/home)
186
+
A. Slowly loading websites may require a change in webpage design, forassistancein optimizing your website to use an AFD, connect with your website design team or our [Microsoft Solution Providers](https://www.microsoft.com/solution-providers/home)
185
187
> [!NOTE]
186
-
>This issue could take time to review based on the complexity of a website's design and it's file calling instructions
188
+
>Slowly loading websites issue could take time to review based on the complexity of a website's design and it's file calling instructions
187
189
1. **If the collected data shows that performance is ***not*** better at the AFD**, a Support Request is likely required for further investigation. Include a reference to this troubleshooting article and steps taken.
0 commit comments