Skip to content

Commit 48cafe3

Browse files
zareefislamCopilotCopilotam-stead
authored
Added copilot slowness troubleshooting guide (#61551)
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: zareefislam <186110388+zareefislam@users.noreply.github.com> Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com>
1 parent 636f931 commit 48cafe3

2 files changed

Lines changed: 75 additions & 0 deletions

File tree

content/copilot/how-tos/troubleshoot-copilot/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ children:
1111
- /troubleshoot-firewall-settings
1212
- /troubleshoot-network-errors
1313
- /troubleshoot-spark
14+
- /troubleshoot-copilot-slowness
1415
redirect_from:
1516
- /copilot/troubleshooting-github-copilot
1617
- /copilot/how-tos/troubleshoot
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Troubleshooting slow responses from GitHub Copilot
3+
intro: Troubleshooting help for slow responses from {% data variables.product.prodname_copilot %}.
4+
allowTitleToDifferFromFilename: true
5+
versions:
6+
feature: copilot
7+
shortTitle: Troubleshoot slow responses
8+
redirect_from:
9+
- /copilot/troubleshooting-github-copilot/troubleshooting-copilot-slowness
10+
- /copilot/how-tos/troubleshoot/troubleshooting-copilot-slowness
11+
- /copilot/how-tos/troubleshoot/troubleshoot-copilot-slowness
12+
contentType: how-tos
13+
category:
14+
- Troubleshooting Copilot
15+
---
16+
17+
## About the problem
18+
19+
If {% data variables.product.prodname_copilot %} is responding more slowly than expected, the problem may be related to network conditions, local system performance, editor configuration, or connectivity restrictions such as proxies or firewalls. Because {% data variables.product.prodname_copilot_short %} relies on remote services to generate responses, issues that affect communication with {% data variables.product.github %} services can reduce responsiveness or cause delays. The troubleshooting steps below can help you determine whether the problem is caused by your environment or by a broader service issue.
20+
21+
If {% data variables.product.prodname_copilot_short %} is responding slowly, work through the following troubleshooting steps.
22+
23+
## Check your internet connection
24+
25+
Make sure you have a stable, high-speed internet connection. Slow or inconsistent connectivity can increase latency and affect how quickly {% data variables.product.prodname_copilot_short %} returns responses.
26+
27+
## Check the GitHub status page
28+
29+
Visit the [GitHub status page](https://www.githubstatus.com/) to confirm whether there is an ongoing incident affecting {% data variables.product.prodname_copilot_short %} or related GitHub services.
30+
31+
## Update your editor and {% data variables.product.prodname_copilot_short %} extension
32+
33+
Make sure your editor and the {% data variables.product.prodname_copilot_short %} extension or plugin are up to date. After updating, restart your editor.
34+
35+
## Check for extension conflicts
36+
37+
Temporarily disable other extensions or plugins, especially ones related to AI coding assistants, linting, formatting, or code analysis. Conflicts between extensions can sometimes affect editor responsiveness and make {% data variables.product.prodname_copilot_short %} appear slow.
38+
39+
## Try a smaller or simpler file
40+
41+
{% data variables.product.prodname_copilot_short %} may respond more slowly in very large files or in projects with high complexity. Test whether performance improves in a smaller file or after splitting large files into smaller units.
42+
43+
## Test in a new project or workspace
44+
45+
Open a new minimal project or workspace and test {% data variables.product.prodname_copilot_short %} there. If response times improve, the issue may be related to the size, dependencies, or configuration of your main project.
46+
47+
## Review system resource usage
48+
49+
Check CPU and memory usage on your machine. High system load or limited available resources can slow down your editor and affect how quickly {% data variables.product.prodname_copilot_short %} responds.
50+
51+
## Check proxy, VPN, and firewall settings
52+
53+
If you use a proxy, VPN, firewall, or security software that inspects web traffic, verify that it is not blocking or interfering with connections required by {% data variables.product.prodname_copilot_short %}. If you work behind a corporate proxy or firewall, you may need to review your organization's network configuration and make sure to follow [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-firewall-settings).
54+
55+
## Review logs for errors or timeouts
56+
57+
Check your editor logs for errors, timeouts, or connectivity problems.
58+
59+
* In **Visual Studio Code**, open the **Output** panel and select **GitHub Copilot** from the dropdown.
60+
* In **JetBrains IDEs**, open the logs from the **Help** menu.
61+
62+
For more information, see [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/view-logs?tool=vscode#viewing-and-collecting-log-files). Save any relevant logs if you need to report the problem.
63+
64+
## Try a different network or device
65+
66+
If possible, test {% data variables.product.prodname_copilot_short %} on a different network or another device. This can help determine whether the issue is specific to your current environment.
67+
68+
## Check GitHub Docs and known issues
69+
70+
Review [AUTOTITLE](/copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues), similar reports, or environment-specific guidance.
71+
72+
## Contact GitHub Support with diagnostic details
73+
74+
If the problem persists, collect relevant diagnostic information before contacting GitHub Support. Include your editor and {% data variables.product.prodname_copilot_short %} extension or plugin versions, steps to reproduce the problem, example files if available, and any related log messages or errors.

0 commit comments

Comments
 (0)