How do I optimize CPU performance for PSM?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PAM Self-Hosted Articles
6 min read
L1 Bithead
No ratings
How do I optimize CPU performance for PSM?

Steps

The general recommendations below can be used to enhance the CPU performance of PSM Servers. These recommendations are relevant for implementations with both physical and virtualized PSM servers (VMs).

Enhancing CPU performance of PSM: 
The following changes are recommended for enhancing performance and stabilizing loaded PSM implementations.

1. Disable RemoteApp:
- Disabling RemoteApp will improve performance. v9.7+ Introduced the ability to selectively disable RemoteApp for specific connections, but will not directly improve performance.

2. Upgrade to PSM v9.7+:
- Upgrading PSM to v9.7+ will allow you to disable RemoteApp selectively for specific connections, but will not directly improve performance.

3. Changes in Timeout Values in PSM Connection Components:
- These changes will help with ensuring stability of loaded environments, but will not directly improve performance.
- Recommended timeout values will determine the amount of time the end-user will need to wait on specific failure scenarios, so this should be considered when setting higher timeout values.
- In loaded environments, configuring timeout values that are double or triple the default values will probably suffice for most implementations.
--- Configuration locations:
----- Connection Components-->{ConnectionComponent}-->Target Settings-->ConnectionComponentInitTimeout
----- Connection Components-->{ConnectionComponent}-->Target Settings-->Lock Application Window-->Timeout
----- Privileged Session Management-->General Settings-->Connection Client Settings-->Capabilities-->SSH Keystrokes Audit-->Default Settings-->AuditCommunicationTimeout
----- Privileged Session Management-->General Settings-->Connection Client Settings-->Capabilities-->SSH Keystrokes Audit-->Default Settings-->ConnectionComponentGracefulTerminationTimeout
----- Privileged Session Management-->General Settings-->Connection Client Settings-->Capabilities-->SSH Keystrokes Audit-->Default Settings-->AuditServerInitializationTimeout
----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->VirtualChannelTimeout
----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->RecorderConnectionTimeout
----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->SessionKeeperConnectionTimeout
----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->SessionKeeperShutdownTimeout
----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->SessionLauncherTimeout
----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->InitSessionTimeout

 
4. Reduce recorded frames per second:
- This change will greatly improve performance, however it is recommended to avoid reducing the number of recorded-frames-per-second too much (below 3 frames per second) so the video recording will not miss important session activity.
--- Configuration location:
----- Privileged Session Management-->General Settings-->Recorder Settings-->FramesPerSecond

 
5. Consider disabling video recording for SSH sessions:
- Since the number one consumer of CPU resources in PSM is the video recording of the session, you may want to consider disabling video recordings for specific types of sessions (or specific platforms).
- SSH sessions are audited and command-line based and therefore are good candidates for not having video recordings.
 
6. Limit session resolution:
- On sessions with RemoteApp disabled, consider lowering the session resolution of the connection component so video recording resolution will decrease and improve performance.
 
7. Best practices for PSM benchmark testing:
- Avoid loading the client machine as well as the target machine (Client -> PSM -> Target)
--- Monitor CPU and memory load on those machines.
--- It is advised to perform capacity planning before performing any tests so additional machines can be added as required.
- Disable trace logging on the PSM machine (both under Server Settings and Connection Client Settings).
- On tests which involve the utilization of the PSM RemoteApp feature, take into account the use of multiple monitors on the client machine (or virtual desktops in case of connecting the client machine via RDP from another machine). Decreasing the video recording resolution will improve performance. On non-RemoteApp tests, take into account the resolution of the connection component being tested.

Q:

How do I optimize CPU performance for PSM?

 

A: 

The general recommendations below can be used to enhance the CPU performance of PSM Servers. These recommendations are relevant for implementations with both physical and virtualized PSM servers (VMs).

 

Enhancing CPU performance of PSM:

 

The following changes are recommended for enhancing performance and stabilizing loaded PSM implementations.

 

 

1. Disable RemoteApp:

- Disabling RemoteApp will improve performance. v9.7+ Introduced the ability to selectively disable RemoteApp for specific connections, but will not directly improve performance.

 

2. Upgrade to PSM v9.7+:

- Upgrading PSM to v9.7+ will allow you to disable RemoteApp selectively for specific connections, but will not directly improve performance.

 

3. Changes in Timeout Values in PSM Connection Components:

- These changes will help with ensuring stability of loaded environments, but will not directly improve performance.

- Recommended timeout values will determine the amount of time the end-user will need to wait on specific failure scenarios, so this should be considered when setting higher timeout values.

- In loaded environments, configuring timeout values that are double or triple the default values will probably suffice for most implementations.

--- Configuration locations:

----- Connection Components-->{ConnectionComponent}-->Target Settings-->ConnectionComponentInitTimeout

----- Connection Components-->{ConnectionComponent}-->Target Settings-->Lock Application Window-->Timeout

----- Privileged Session Management-->General Settings-->Connection Client Settings-->Capabilities-->SSH Keystrokes Audit-->Default Settings-->AuditCommunicationTimeout

----- Privileged Session Management-->General Settings-->Connection Client Settings-->Capabilities-->SSH Keystrokes Audit-->Default Settings-->ConnectionComponentGracefulTerminationTimeout

----- Privileged Session Management-->General Settings-->Connection Client Settings-->Capabilities-->SSH Keystrokes Audit-->Default Settings-->AuditServerInitializationTimeout

----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->VirtualChannelTimeout

----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->RecorderConnectionTimeout

----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->SessionKeeperConnectionTimeout

----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->SessionKeeperShutdownTimeout

----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->SessionLauncherTimeout

----- Privileged Session Management-->General Settings-->Session Settings-->Advanced Settings-->InitSessionTimeout

 

4. Reduce recorded frames per second:

- This change will greatly improve performance, however it is recommended to avoid reducing the number of recorded-frames-per-second too much (below 3 frames per second) so the video recording will not miss important session activity.

--- Configuration location:

----- Privileged Session Management-->General Settings-->Recorder Settings-->FramesPerSecond

 

5. Consider disabling video recording for SSH sessions:

- Since the number one consumer of CPU resources in PSM is the video recording of the session, you may want to consider disabling video recordings for specific types of sessions (or specific platforms).

- SSH sessions are audited and command-line based and therefore are good candidates for not having video recordings.

 

6. Limit session resolution:

- On sessions with RemoteApp disabled, consider lowering the session resolution of the connection component so video recording resolution will decrease and improve performance.

 

7. Best practices for PSM benchmark testing:

- Avoid loading the client machine as well as the target machine (Client -> PSM -> Target)

--- Monitor CPU and memory load on those machines.

--- It is advised to perform capacity planning before performing any tests so additional machines can be added as required.

- Disable trace logging on the PSM machine (both under Server Settings and Connection Client Settings).

- On tests which involve the utilization of the PSM RemoteApp feature, take into account the use of multiple monitors on the client machine (or virtual desktops in case of connecting the client machine via RDP from another machine). Decreasing the video recording resolution will improve performance. On non-RemoteApp tests, take into account the resolution of the connection component being tested.

Rate this article: