Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 236436

Re: Splitting up a nVidia GRID K2's GPUs?

$
0
0

Interesting about vDGA.  I wonder why we have a worse experience, since there are really no settings per se to get vDGA to work with View.  We are also using the latest View release (5.2).  You know on second thought I need to go back and check this with the Quadro 4000 we have.  I just remembered the last time I was messing with this (and the bad experience I mentioned) I was using a V7900 FirePro card (Direct-Pass GPU).  It sounds like this is optimized for only nVidia cards right now?

 

We use a 3D map application which can tax the GPU a bit, but we actually get a good frame rate with the application itself (35-45 FPS).  Our issue is getting a good PCoIP session FPS (which I have mentioned before on these forums).  The latest config we have is using tera2 zero clients with an apex card in the server.  We run four monitors on our zero client and on the 3D map display when moving around quickly we avg 15-19 FPS (PCoIP session frame rate).  If we are also playing video on one of the other displays while moving around in the map app the avg frame rate drops to 13-15 FPS.  If we do not use a zero client these frame rates drop quite significantly.  The apex card gave us about a 2-3 FPS bump as well as CPU offload.  I guess we are probably getting close to the limits of the PCoIP session's capabilities with this setup?

 

The reason we have to mix VDI and Direct-Pass GPU VMs is the requirement to be able to access all the different VMs from the same end point and also only use one type of client device (zero client).  If we used a regular computer with the software view client and the citrix receiver (when connecting to the Direct-Pass GPU vms) the vSGA VMs would suffer very badly (the PCoIP session frame rate that is).


Viewing all articles
Browse latest Browse all 236436

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>