add troubleshooting

docs/guides/cloud/debugging/test-replay.mdx

@@ -136,12 +136,20 @@ If you'd like not to capture test data for replay and debugging purposes you can
 
 ## Troubleshooting
 
-If Test Replay is not present or disabled in Cypress Cloud:
+**If Test Replay is not present or disabled in Cypress Cloud:**
 
 1. Confirm runs have been recorded to Cypress Cloud using Cypress `v13` or later.
 2. Ensure tests were recorded using a Chromium-based browser(Chrome, Edge, Electron).
 3. Check that Test Replay is enabled in project settings.
 
+**If performance loss is experiecned in Cypress with Test Replay enabled:**
+
+Cypress may become less performant under certain circumstances with Test Replay. You may be able to balance performance by taking some additional measures.
+
+Cypress uses a powerful [command log](/guides/core-concepts/cypress-app#Command-Log) locally to display every command executed in your spec. Yet, the command log in the test replay on Cypress Cloud is recreated at a _later_ time. If you are not using screenshots or video or don't need the command log displayed in these artifacts, you can [disable the command log](/guides/references/troubleshooting#Disable-the-Command-Log) when running the test.
+
+This should positively affect test speed without loosing the interactive benefit of the command log during the Test Replay. You can still keep the command log enabled for tests run in non-Chromium browsers to gain its benefit in your test artifacts.
+
 ## See also
 
 - [Test Replay FAQ](/faq/questions/cloud-faq#Test-Replay)