Depending on what specifically is running slow will change how this can be answered. If you are noticing that your Jump Shortcut sessions (RDP, SSH, ect) are sluggish then it’s a good idea to check the Jumpoints resource's and ensure that they are scaled up enough to handle the load, if you utilize BYOT, this may consume more CPU than would otherwise be expected so that’s one thing to look out for.
Depending on what specifically is running slow will change how this can be answered. If you are noticing that your Jump Shortcut sessions (RDP, SSH, ect) are sluggish then it’s a good idea to check the Jumpoints resource's and ensure that they are scaled up enough to handle the load, if you utilize BYOT, this may consume more CPU than would otherwise be expected so that’s one thing to look out for.
Can you give some more insight to why using BYOT RDP would use more CPU on a jumpoint? I was under the impression it’d be less impact on the jumpoint compared to using the built-in bomgar RDP since it was just passing through basically. I’m not doubting btw, I would just love to understand more about it.
Hey @idontwanna, sure. The driving point of the CPU utilisation being heavier when using BYOT is more to do with recording the session than anything. If you don’t have session recordings enabled, the difference is much more minimal.