Troubleshooting Video Latency on Non-Persistent VM with ControlUp

A user asked about troubleshooting video latency on a non-persistent VM, and it was suggested to use User Session Details in Solve as the best starting point. If Remote DX was installed, they can also watch session relevant latency, CPU, RAM and other metrics in a single place. Script Action can be used for advanced data collection. The Network Latency graph may be legit, but there was a known issue with the Linux RDX plugin. A new beta version which fixes this issue will be available soon. After sifting through the data, 3.75GB of RAM usage was found – they will look at adjusting graphics settings with Horizon View.

Read the entire ‘Troubleshooting Video Latency on Non-Persistent VM with ControlUp’ thread below:

looking to troubleshoot video latency on a non persistent VM. Will User Session Details in Solve be the best place to start?

yep, indeed

if Remote DX is also enabled, you can watch the session relevant latency, CPU, RAM and all other relevant metrics in a single place

if you need more specific virtual channel details (assuming this is what you meant with “video latency”), we can use Script Action for real-time advanced data collection

https://www.controlup.com/script-library-posts/analyze-hdx-bandwidth/

thx. No Remote DX is installed. Is this odd?

i see Remote DX is installed but Client score says Insufficient

@member with the SBA work for VDI Clients or just Citrix?

The script is for Citrix sessions…

And the Network Latency graph may be legit, because we only collect remoting protocol latency data when the session is active

you can cross reference the latency timeline to the gantt that shows the session state over time

RDX score – looks like a known issues with our Linux RDX plug-in (where WiFi signal shows 0%), I think we have a fix in the works, pls contact Support about this

We have a new beta coming out for Remote DX Linux very soon that addresses the wifi 0% issue. @member I assume you will share when this beta is available in #controlup_product-betas?

i sifted thru all the data and didn’t find any metrics to explain poor video other than 3.75GB of 4GB of RAM usage. We are going to look at graphics settings on Horizon View as they look like they could use some tweaking. Not sure if this is something we could have seen with ControlUp or not. I’ll update later if that helps fix the issue.

Continue reading and comment on the thread ‘Troubleshooting Video Latency on Non-Persistent VM with ControlUp’.  Not a member? Join Here!