Update troubleshooting.mdx to include how to debug slowness (#1009)

<!-- Explain the changes introduced in your PR -->

## Pull Request approval

You will need to get your PR approved by at least one member of the
Sourcegraph team. For reviews of docs formatting, styles, and component
usage, please tag the docs team via the #docs Slack channel.

Author: enriquegh

docs/cody/troubleshooting.mdx

@@ -13,6 +13,19 @@ If you're experiencing issues with Cody not responding in chat, follow these ste
 - Ensure you have the latest version of the [Cody VS Code extension](https://marketplace.visualstudio.com/items?itemName=sourcegraph.cody-ai). Use the VS Code command `Extensions: Check for Extension Updates` to verify
 - Check the VS Code error console for relevant error messages. To open it, run the VS Code command `Developer: Toggle Developer Tools` and then look in the `Console` for relevant messages
 
+### Cody responses/completions are slow
+
+If you're experiencing issues with Cody's responses or completions being too slow:
+
+- Ensure you have the latest version of the [Cody VS Code extension](https://marketplace.visualstudio.com/items?itemName=sourcegraph.cody-ai). Use the VS Code command `Extensions: Check for Extension Updates` to verify
+- Enable verbose logging, restart the extension and reproduce the issue seen again (see below `Access Cody logs` for how to do this
+- Send information to the our Support Team at [email protected]
+
+Some additional information that will be valuable:
+- Where are you located? Any proxies or firewalls in use?
+- Does this happen with multiple providers/models? Which models have you used?
+
+
 ### Access Cody logs
 
 VS Code logs can be accessed via the **Outputs** view. You will need to set Cody to verbose mode to ensure important information to debug is on the logs. To do so: