System Configuration Suggestions for LEAPWORK

All three components of the LEAPWORK Platform Edition can be installed on the following versions of Windows:

• Window 7 (Service Pack 1)*, Windows 8.0 + 8.1, Windows 10
• Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 

*Please note, you may experience performance challenges if you run complex automation flows on Windows 7, due to the operating system’s low memory constraints.

The OSX version of the LEAPWORK Agent can be installed on OSX 10.8 or newer.

Please note, .Net Version 4.8 is required to install LEAPWORK. The user can download and install .Net Version 4.8 using the following link.

Typically, the Studio and Agents are installed on desktop versions, whilst the Controller is installed on a Windows server. Some operating system does not work remotely due to technology challenge please check the following requirements for remote servers and operating systems, similarly click here to read about the Prerequisite for using Windows Credential for auto-login.

The studio should be installed on the user’s work station hence it's configuration remains the same for Platform and Enterprise editions. The studio is comparable to a normal Office installation, so, in most cases, no special configuration is required.

The recommended hardware configuration for the Studio is:

• 8 GB RAM as a minimum; 16 GB is recommended
• Intel i5 CPU as a minimum
• SSD based internal storage. 20 GB to begin with
• A wired internet connection

LEAPWORK's Platform and Enterprise Editions each come with their own suggested system configurations for the Agent and Controller/server. This page will give you details of both:

1. Platform Edition
2. Enterprise Edition

Platform Edition

Controller

The Controller is the central hub in the LEAPWORK system and needs to be configured to accommodate the workload. The workload depends on various factors. These include:

• The number of automation flows
• The complexity and duration of automation flows
• The frequency of automation flow execution

The recommendation is to start with a standard server configuration and monitor the Controller machine's memory usage, I/O activity, CPU usage, etc. The user can then down/upgrade the machine as required. A standard server configuration could be:

• 16 GB RAM
• 4-6 cores
• Flexible and fast disc system (SSD, SAN, or similar. 40 GB to begin with)

The Controller can run on both physical and virtual servers.

Please note, if the user wants to install all components on one machine, the following hardware configuration is required:

• 16 GB RAM
• 4-6 cores
• 60 GB SSD

Agent

The Agent is used for executing automation flows. Whilst deploying the Agent in the Data Center, it may not be possible to obtain a Windows desktop version. Therefore, the Agent will also run on a Windows Server with Desktop Experience enabled. The Server is installed on a Windows server. Here is how to choose the configuration for the Agent machine:

• Simulating applications for an end-user:
  In this case, the machine should be as similar as possible to the end-users' machine. This will increase the reliability of the automation flows. However, we recommend that the CPU has at least two cores.
  The recommended hardware configuration, in this case, would be: 
  • 8 GB RAM as a minimum; 16 GB is recommended
  • Intel i5 CPU in a physical machine. In the case of a virtual machine CPU, there should be at least two cores 
  • SSD-based internal storage
    
    
• Running automation flows in parallel:
  In the case of executing web automation flows, it is possible to set up an Environment that points to a Selenium Grid. Selenium Grid allows multiple browsers to run web automation flows in parallel on the same machine. The more powerful the machine, the more browsers can run in parallel.
  In this case, a recommended hardware configuration (assuming 4 parallel browser executions) would be as follows:
  • 16 GB RAM
  • 4-6 cores
  • Flexible and fast disc system (SSD, SAN, or similar. 30 GB to start with)

Enterprise Edition

For the Enterprise Edition, please be aware that infrastructure configurations vary widely from company to company and may impact system requirements. For example, the performance of LEAPWORK’s software can be significantly impacted by high-latency or low-throughput network conditions, virtual server configurations with noisy neighbors, degraded SAN disk performance at write-time, and many other factors.

For this reason, we suggest an agile approach in which one or more environments are initially set up in real-life conditions and adjusted as usage is increased during the first 90 days of operation.

In general, remember:

• Hardware requirements for Agents are also dependent on the application(s) under test, particularly RAM and CPU. You may find that dimensioning of the Agent is actually driven by this instead.
• The more disk space you have, the more data you can store – the alternative is harsh retention policies.
• The more CPU cores you have, the faster processing and parallelization will work.
• Use high-speed SSDs for data storage with high write or read patterns, and combine with extra RAM.

The following table shows the suggested hardware configurations for LEAPWORK's Enterprise Edition Servers, Agents, and MS SQL Server database:

Typically, the Studio is installed on the desktop version. We also recommend this for the Agent.
However, when deploying the Agent in the Data Center, it may not be possible to obtain a Windows desktop version. Therefore, the Agent will also run on a Windows Server with Desktop Experience enabled. The Server is installed on a Windows server.

For any clarification, please contact our Priority Support.