Poor / slow performance within PSM sessions for end users (4229765)

Poor / slow performance within PSM sessions for end users

Is there any way to improve the performance of PSM sessions?

If you experience slow performance, screen lag or unresponsiveness when connecting to PSM sessions, you can adjust the Connection Options to improve performance.

In the Session Request Management window, select the "Connection Options" tab. Uncheck the box for "Use Default Connection Options".

Experiment with modifying the available options (such as setting "Experience" to 56k, Compression to "On" and turning "Cache Bitmaps On") to see if your performance improves.

Enabling the feature "Cache Bitmaps" (persistent bitmap caching), generally improves performance and reduces network traffic at the cost of a slightly longer startup and disk space.

Outside of these options, the performance of PSM sessions is down to the available network bandwidth/latency between the users client machine and TPAM (or a DPA) and from TPAM/DPA to the Target system.  If QOS (Quality of Service) settings are available on the network increase the priority of SSH and RDP traffic.

If the performance is slower than accessing through a VPN, ensure the internet or externally facing routers and firewalls have been optimized for efficient performance to reduce the amount of connection delay or network latency (e.g. turn off packet inspection IDS/IPS).

There are differences in the way the session is captured between the native RDP session vs a TPAM / PSM session, meaning TPAM PSM will have more overhead and have lower performance than native RDP sessions.
RDP client connects directly to the target, where as TPAM PSM has a greater overhead to allow for the recording of the session. The hops involved for a PSM session: Java Applet-> TPAM or DPA (through port SSH/22) -> RDP (through 3389) to the target machine.