Slowness in Live Authoring (LA)

Article Overview:

This article will provide insights into how to approach and resolve slowness issues in Live Authoring (LA).

Problem Statement:

Customers may experience slowness in Live Authoring (LA), where certain steps take an extended amount of time to execute. Investigating the root causes of this slowness is necessary for improving performance.

Solution:

The issue appears to be related to network traffic for the specific page being tested. Upon reviewing the network events, none seem to take an extended amount of time to explain the observed delays. However, several additional tabs were open (as seen in a provided screenshot), which align with network logs lacking associated time values.

Steps to Investigate and Mitigate Slowness:

1. Analyze Network Traffic:

   • Open the Network tab in browser developer tools during Live Authoring.
   • Identify any requests that may be taking longer than expected.

2. Check for Unintended Background Activity:

   • Verify if additional browser tabs are open and consuming network resources.
   • Ensure no unnecessary background processes are running on the page

3. Disable the "Wait for Network Traffic" Feature (If Applicable):

   • Navigate to Virtuoso settings and check if the "Wait for Network Traffic" option is enabled.
   • Consider disabling it if network delays are not relevant to test execution.
     
     

4. Review Any Active Extensions or Scripts:

   • Check if browser extensions or user scripts are interfering with the execution.
   • Disable extensions temporarily and reattempt execution.
     
     

5. Validate System Performance and Resource Utilization:

   • Monitor CPU, memory, and network usage during Live Authoring to ensure they are within optimal limits.
   • Close unnecessary applications or browser tabs that may be consuming resources.
     
     

6. Test on a Different Network or Device:

   • Switch to an alternative network to rule out network congestion issues.
   • If possible, execute Live Authoring on another machine to compare performance.

Example:

• Scenario: A customer reports excessive slowness in Live Authoring, where a particular step takes significantly longer to execute.
• Solution: The "Wait for Network Traffic" setting was disabled, unnecessary tabs were closed, and the network logs were analyzed. This improved execution speed.

By following these steps, users can identify and resolve slowness issues in Live Authoring, ensuring a smoother test execution experience.