Articles in this section

System Configuration Suggestions for Leapwork - Enterprise Edition

Avatar
Rishi Gaurav
  • Updated
Follow

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 operating system and SQL server versions supported for the Enterprise Edition 

Operating System Supported MS SQL Supported
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

MS SQL (version 13), 2017 (version 14), 2019 (version 15), Azure SQL is also supported.

MS SQL Edition Supported - SQL Enterprise (Recommended), SQL Standard.

MS SQL Edition Not Supported - SQL Express, SQL Developer.

 

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

Installation scenario

Leapwork Server

Leapwork Agent

MS SQL Server

Multiple teams, medium usage

  • 25 users, 500 flows, 10 agents, 2 runs per day
  • 500 * 10 * 2 = 10,000 flows run per day
  • 500 keyframes per-flow run, 100 bytes per keyframe = 10,000 * 500 * 100 = 500 MB new run data per day

 

 

  • 16 GB RAM
  • 64-bit, 4-8 cores
  • 500 GB regular drives
  • Virtual machines recommended for most scenarios - avoid noisy neighbors

 

 

  • 4-16 GB RAM
  • 64-bit, 2-4 cores
  • 100 GB regular drive
  • Virtual machines recommended for most scenarios - avoid noisy neighbors

 

  • 16 GB RAM
  • 64-bit, 4-8 cores
  • 1 TB regular drives
  • Shared MS SQL Server instance recommended - avoid noisy neighbors

Multiple teams, high usage

  • 25 users, 500 flows, 25 agents, 10 runs per day
  • 500 * 25 * 10 = 125,000 flows run per day
  • 500 keyframes per-flow run, 100 bytes per keyframe = 125,000 * 500 * 100 = 6.5 GB new run data per day

 

  • 32 GB RAM
  • 64-bit, 16 cores
  • 1 TB SSDs
  • Physical machine recommended
  • Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage
  • 4-16 GB RAM
  • 64-bit, 2-4 cores
  • 100 GB regular drive
  • Virtual machines recommended for most scenarios - avoid noisy neighbors
  • 32 GB RAM
  • 64-bit, 16 cores
  • 2 TB SSDs
  • Physical machine recommended
  • A shared instance may be relevant, depending on spikes in usage

Department, high usage

  • 50 users, 5,000 flows, 50 agents, 10 runs per day
  • 5000 * 50 * 10 = 2,500,000 flows run per day
  • 500 keyframes per-flow run, 100 bytes per keyframe = 2,500,000 * 500 * 100 = 125 GB new run data per day
  • 32-64 GB RAM
  • 64-bit, 16 cores
  • 1 TB SSDs
  • Physical machine recommended
  • High-throughput, low-latency network with Agents and MS SQL Server recommended
  • Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage
  • 4-16 GB RAM
  • 64-bit, 2-4 cores
  • 100 GB regular drive
  • Virtual machines recommended for most scenarios - avoid noisy neighbors
  • 64 GB RAM
  • 64-bit, 16 cores
  • Large disk array Shared instances and virtual machines not recommended
  • Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage

Company or site-wide, high usage

  • 250 users, 15,000 flows, 250 agents, 10 runs per day
  • 15000 * 250 * 10 = 37,500,000 flows run per day
  • 500 keyframes per-flow run, 100 bytes per keyframe = 37,500,000 * 500 * 100 = 2 TB new run data per day
  • 64 GB RAM
  • 64-bit, 16 cores
  • 1 TB SSDs
  • Physical machine recommended
  • High-throughput, low-latency network with Agents and MS SQL Server recommended
  • Multiple (departmental or project-related) servers recommended
  • 4-16 GB RAM
  • 64-bit, 2-4 cores
  • 100 GB regular drive
  • Virtual machines recommended for most scenarios - avoid noisy neighbors
  • 64 GB RAM
  • 64-bit, 16 cores
  • Large disk array
  • Shared instances and virtual machines not recommended
  • Consider splitting into multiple servers, depending on the network, disk performance, and spikes in usage

 

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. 

Related articles

Comments

0 comments

Please sign in to leave a comment.