PRA Sites and Engines for Linux are deprecated. Sites and Engines previously deployed and activated, will continue to function normally.
Use Engine Management with PRA capabilities for any new deployments.
Customers will be able to upgrade their previously deployed engines manually or with a single-click (coming soon!)
Customers should continue to use the guidance provided below on this page for sizing their Linux and Windows hosts when running Platform Engine and PRA capabilities.

Sizing Guidance for PRA Engine Linux Hosts

The PRA engine runs on supported Linux hosts (for more information, see PRA Requirements) and is used to establish connections between a user’s browser and target systems within the customer’s private network. When a connection is initiated, the PRA service in the Delinea Platform selects a single PRA engine from a set of engines associated with the parent site, to host the connection.

This document offers guidance to users to determine what hardware configuration is needed to host the PRA engine depending on the number of concurrent PRA session that engine needs to host.

Size testing was performed on PRA engine hosts running Ubuntu version 18.04.3 LTS equipped with 4 Intel® Xeon® E5-2609v3 CPU cores @ 1.9 GHz, with 8GB of RAM, on a 10mbps network.

Sessions were tested on a site with a single PRA engine, as well as a site associated with two PRA engines. Multiple concurrent sessions were opened, kept running for 30 minutes and then closed. The following actions were performed on the remote target machines after connection was established:

  1. SSH: Login to a remote Linux server and run “top”.

  2. RDP: Login to a remote Windows server and run a batch script that produces output similar to that of a typical command-shell script.

Session recording was disabled in both test cases.

Session Type # of PRA Engines # of Concurrent Sessions % Per-engine CPU usage % Per-engine Memory usage
SSH 1 200 8 40
SSH 2 400 8 38
RDP 1 200 19 40
RDP 2 400 17 41

While a Single PRA engine can handle 200 SSH or RDP sessions concurrently, your actual capacity may vary depending on the specific activities that are being carried out on the remote target machine. For example, viewing a video clip on the remote machine on RDP will put very different load on PRA as compared to running vim to edit a text file on a remote SSH session. Performance test data also indicates that PRA engine performance is more dependent on memory and bandwidth than CPU speed or power.

The network latency between the end-user’s browser and the Delinea Platform, or the latency between the PRA engine and the target server also affects the user-experience.

We recommend the following steps when experiencing PRA performance issues that may be associated with PRA engines:

  1. Use system monitoring tools to determine whether any specific resource like memory, network bandwidth, CPU utilization is running at unacceptably high levels. If possible, increase the corresponding hardware or virtualization resources.

  2. Deploy more engines to the parent site.

  3. Check the network latency between:

    1. The PRA engine and the Delinea Platform tenant.

    2. The PRA engine and target machines

  4. Contact Delinea Support.