Skip to Content

Welcome to the 

Sahi Pro Customer Portal

Access your tickets, forums, courses and more, all in one single place

Sign up

You need to be registered to interact with the community.
This question has been flagged
1 Reply
335 Views

Hi,


We are experiencing an issue during extended test execution cycles. During long execution runs, the playback performance gradually degrades, and multiple scripts eventually get aborted.

Could you please help us understand the following?

  • Why does the performance slow down over time?

  • Could this be related to memory leaks, resource utilisation, or configuration settings?

  • What logs or diagnostic details do you require from our end for further analysis?

Please let us know the next steps to investigate this issue.

Thank you.

Avatar
Discard

Hi Kristin,

Ensure that you are using the latest version of Sahi Pro, as performance-related issues are often addressed in newer releases.

Possible Causes and Recommended Resolutions:
  1. Enable Sahi Auto Threading

    Ensure that the Auto Threading feature is enabled in userdata.properties:

    • sahi.auto_thread.enabled=true

    • Set sahi.threshold.cpu_usage to a value between 70 and 90.

      The optimal value may vary depending on the system configuration, so it is recommended to run the scripts multiple times to determine the best value for your environment.

  2. System Resource Availability

    Playback may slow down if other applications are consuming significant RAM or CPU resources.

    Please ensure that sufficient system resources are available for the automation runs.

  3. Disable Browser Background Tab Throttling

    Chromium-based browsers such as Google Chrome and Microsoft Edge use Background Tab Throttling for power optimization.

    This can slow down automation running in background tabs.

    To disable this feature:

    • Open browser_types.xml

    • Add the following option to the browser startup parameters:

    --disable-background-timer-throttling
    

    Example configuration:

    <options>--no-default-browser-check --user-data-dir=$userDir\browser\chrome\profiles\sahi$threadNo --proxy-server=127.0.0.1:$port --disable-popup-blocking --always-authorize-plugins --allow-outdated-plugins --enable-npapi --incognito --disable-background-networking --disable-component-update --disable-renderer-backgrounding --disable-backgrounding-occluded-windows --disable-background-timer-throttling</options>
    
  4. AWS Instance Configuration

    If the execution is running on Amazon Web Services instances, it is recommended to enable Unlimited Mode:

    • Log in to AWS Management Console

    • Right-click the instance used as the Sahi node

    • Go to Instance Settings → Change Credit Specification

    • Enable Unlimited Mode

Avatar
Discard
Related Posts Replies Views Activity
1
Mar 26
279
1
Mar 26
296
1
Mar 26
405
1
Feb 26
354
1
Mar 26
361