This message was deleted.

depends on what trading app, but might need a vgpu.

Trade Book loads multiple trades on screen in Citrix VDI there is delay for 3-5mins

There’s a blog from @Rody Kossen’s team on virtualizing trader desktops, that’s a decent start

This one is a good start: https://www.citrix.com/blogs/2022/09/22/how-to-give-financial-traders-the-citrix-hdx-performance-they-need/

Thanks @Kees Baggerman for the start and also Thanks @Rody Kossen for sharing the blog post...

Well, as you can read in the blog, for this use case a GPU is definitely a must. And that's not "a Citrix" thing but also from an Application perspective

Did you check the system requirements of the app before installing/configuring it in an (assuming) VM?

I am doing a POC

How many screens are you driving? What are the specs of a workstation that would run this app now?

2 Monitor

I think Moonshot is also used in trading apps - not really "virtualization" anymore though.

moonshot is being discontinued, though. i think its within the next 2 years

Installing VDA 2209

Don't do traders without GPU. Seriously, you might as well just quit if you don't (assuming you're talking investment banks, and not, for example, energy traders)

Ok James... you did any project with these same concept?

In the middle of one, Rody is helping me 🙂 We have very high spec RPC machines with two GPUs and stacks of RAM and CPU, and they still run like shit

understood

Did you reconnect to the session when you applied the regvalue?

I rebooted VDI

Can you share a screenshot of the registry?

Now when i login through citrix session that registry key is not showing

Non-persistent VDI?

Persist

There you go..

Device Type is same

Timer period is not needed for 2209 ( as stated in the article). I still recommend to look at our recommendations regarding sizing and GPUs

Yes sure will consider in PROD SETUP

@Rody Kossen curious after reading this https://www.citrix.com/blogs/2022/09/22/how-to-give-financial-traders-the-citrix-hdx-performance-they-need/ Is the CitrixIDD recommendation a blanket recommendation even in cases with a support Nvidia GPU? I see an older article that says it's just to be used for workarounds. In really small scale testing I'm seeing pretty similar performance. Curious is it's worth making a change as we're always looking for ways to improve performance/reliability

If you don't have any issues now I would not change it. One reason could be you want to be able to view protected content, for example an protected email. Other than that, if you have no issues I would not change it now

No performance issues to note, just more reliability issues (single session vdas disconnecting and not reconnect able without a hard reboot). At wits end so wondering if similarly performant if it would reduce interoperability issues

Which VDA version are you running? With which nvidia version?

2203 CU1.1 VGPU 13.3 We've seen the issue since 1912 cu3 or so. At that point rdping to the affected vm was enough to fix it, but at this point we have to restart to clear it. I "should" open a case with support on this but it's uncommon enough that we can't make it occur on demand and users aren't willing to let us troubleshoot when it does occur

Hmm, can't say that the issue sounds familiar. Hope you can open a support case and upload a cdf trace. But to get it correctly, user is working and suddenly they get disconnected and can't reconnect? Any traces in event viewer? What is your Hypervisor?

Vmware Yea, working normally, normal load on host and guest, and randomly workspace goes black on all the screens, then disconnects a few seconds later. They try to reconnect unsuccessfully. In director I can see the session still shows as active on the VDA. If I PSremote to the machine I can see an active console session but can't disconnect it. If I or they try to rdp it just hangs. Killing LogonUI does nothing for it. Only fix thus far has been to reboot. Citrix related Event logs are clean as are application / system event logs. CDF Trace is a good idea, but didn't think too much about how to kick it off from commandline at the time of the issue, always too frantic to get it fixed (most of our users traders and don't have time to troubleshoot or move to a dr machine during market hours)