Investigating Delays for Dedicated Citrix MCS VDI

A user reported that all applications on their dedicated Citrix MCS VDI, which has 6xCPU and 64GB RAM for running Bloomberg and other heavy apps, have experienced delay, including mouse delays. It was suggested to check the latency Last metric in the RT console, or the latency metrics via the Session Details report in Insights. RemoteDX and Scoutbees were also mentioned as useful tools to check the endpoints network conditions and latency to the backend servers. A temporary license had been applied for to test these products.

Read the entire ‘Investigating Delays for Dedicated Citrix MCS VDI’ thread below:

Hello,

I have the case of a user that is using a Citrix MCS dedicated VDI on a "kiosk" PC with 4 monitors.

The VDI is 6xCPU, 64Gb RAM because he is running Bloomberg and other heavy apps.

Yesterday he had no problem, everything smooth, no latency.

But this morning he calls and says everything is slow, almost blocked.

I checked my ControlUp console and I see nothing wrong basically, see attached real time and Insight for this VDI since yesterday). CPU

I am obviously missing something!

Would Remote DX help me find network latency ?

Thanks in advance, cheers, JCM

With RemoteDX you will get another useful informaiton abt the endpoints network condition. If this user is working from Home you can definetly use RemoteDX to see potential WiFi, LAN or WAN issues.

If this user is connecting thru a Citrix Gateway you can also check the Gateway within ControlUp if you see some latency…

is it only the application that is slow. do they us other applications on the VDI. outlook or a Browse?

if it a latency issue all applications should show the same symptoms. If they don’t and the VDI is ok that it prob the backend were the issue isif u have scoutbees you could all us that to check ifthere is latency to the backend seversThanks for your answers.

The user is on site, is it still ok with DX?

All apps are slow, i.e. delay in Outlook, in Excel, etc, mouse delays…

I don’t have scoutbees either.

yep you cab use remote DX on site as well

but note sure what it will show 🙂If the CPU / CPU Queue Length / RAM / Disk Latency / User Input Delay metrics all looks OK (and they do look OK), I would look indeed on the protocol metrics

even without Remote DX, you can check the Latency Last metric in the RT console, or the latency metrics via the Session Details report in InsightsTwo last notes:

1. the physical endpoint running the VDI session can be slow (e.g. 100% CPU for example). Edge DX agent on the physical endpoint will give full visibility, and Remote DX in the upcoming 8.8 version will also give visibility to the client CPU
2. If both the VDI endpoint and the physical endpoint looks good, I would try to understand if ALL apps on the VDI are slow, including the local Explorer Shell, or only client-server / Web appsIf even the local Explorer Shell is slow on the VDI endpoint, we may be missing something here, if its just client/server / Web apps that are slow, the VDI network connectivity may be the root cause@member thanks, I will push again to get DX or Scoutbees… I have applied for a temporary licence, I am hoping to test these products as soon as possible

i love scoutbees 🙂

Continue reading and comment on the thread ‘Investigating Delays for Dedicated Citrix MCS VDI’.  Not a member? Join Here!