There have been some recent changes for the RTM versions of Windows 7 and Windows Server 2008 R2 related to where content is rendered (client or host) when remoted over RDP 7. Read on to learn more about what has changed, and how various types of content are remoted in the final version of RDP7.
In pre-release Windows 7 and Windows Server 2008 R2 we provided the ability to remote GDI, DirectX 10.1/DXGI 1.1, Direct2D, Aero Glass experience, and media with Windows Media Player using a client-based rendering technique. This has the advantage of utilizing available client side CPU/GPU resources to do all the rendering and rasterization of the graphical data.
Other content types, such as WPF, Silverlight, Flash, and DirectX 9 applications, were remoted using our enhanced bitmap acceleration feature in R2, where host-side CPU/GPU resources are utilized to perform the rendering and rasterization on the host before sending these bitmaps efficiently over the network.
In the RTM version of Windows 7 and Windows Server 2008 R2, GDI applications, media with Windows Media Player, and Aero Glass will continue using the client-side rendering for remote scenarios as demonstrated in the pre-release version. For the RTM release, client-based rendering will no longer be available for DirectX 10.1 / DXGI 1.1 and Direct 2D applications, instead this type of content will be remoted using host-side resources leveraging the enhanced bitmap acceleration capabilities in R2. This decision was made based on the feedback we received during the engineering and validation process, where the number one requirement was quality and robustness. While this design change may impact the utilization of CPU and GPU resources on the host side for certain use cases, it provides a consistent approach to remoting multiple types of rich (2D and 3D) content across a broad range of rich and thin client devices.
Christopher, both proposals are very reasonable, starting with the point to select the location where rendering work have to be done is very much inline what RDP was doing from the day one. Based on the capability negotiation between client and server, we send GDI/DDI commands to the clients that capable to do the rendering job to free up server’s resources.
With DX apps, similar model did not show the same performance gains, when we were passing DX commands to the client based on the fact that client has GPUs. This model is not completely obvious win, since the DX traffic is much more chatty than GDI/DDI, so it will impact bandwidth usage.
Your case is slightly different, due to some limitations in our remote usage of the host side GPU, we will not be able to take advantage of your CUDA capable NVIDIA driver. For apps, that will be relaying on CUDA instructions, they will have issues to run in remote sessions. All others, those that will use non-CUDA capable functionality of GPUs, they will run just fine, will be rendered on the host and the resulting bitmaps will be sent to a client.
THanks for the reply, Nelly,
Actually, although early CUDA devices were actually GPU's, the NVIDIA Tesla C1060 card is not designed to be used as a GPU. You cannot plug a monitor into a Tesla. The Tesla C1060 does not include any external I/O connectors. The only interface with the C1060 is the PCI-e slot that it is plugged into. NVIDIA calls the Tesla a "computing processor" - not a GPU.
I'm on the application side of things, but there must be some way to tell that the Tesla is not a GPU card.
i am really disapointed trying to use adobe photoshop accelerated graphics on my other computer via remote desktop both windows 7, after paying for 7 ultimate i find out i need server? theres no good information about what i would need to get this working either! windows server? ultimate? the dudes in india transfered my call 8 times to get me a refund after an hour i gave up. i think the problem is pretty obvious, if remote desktop supported accelration for servers or clients properly microsoft would just sell fewer x-boxes, because gamers would just remote into their desktops. aweful customer service, bad documentation, most people moved away from asp years ago, terrible new UI features that make window positioning a battle, windows sound recorder lost 90% of its features, what hell hell happened to microsoft you guys ran out of ideas and outsourced your brains to india?