I was disappointed, but certainly not surprised, to see that Microsoft employees blogging that Visual Studio 2010 performance over remote desktop would almost match, or be slightly slower than Visual Studio 2008 performance.
However, they got some good advice on how to optimize your RDP experience with Visual Studio.
Slow connections:
- On slow connections, change remote desktop connection settings to use 16-bit color.
- If running on high latency connections, select a “high latency” connection speed in RDC options:
- On XP/Vista, grab the new remote desktop client, version 7.0.
- Disable all check boxes except Persistent bitmap caching.
- Also recommended is using a smaller window size (but that may be the most difficult to do).
WPF Application Optimization for Remote Desktop
In addition to the performance tips for Visual Studio, there’s a very nice set of best practices to follow for how to optimize any WPF application for use over remote desktop. Until the long-ago Longhorn promise of truly remoted-WPF applications support is added to the platform, we’ll need to optimize your WPF applications if they may be used over remote desktop.
The worst offender that I’ve encountered in the past is that animations, even hidden behind an opaque element, still cause that area of your application to be sent for each frame of the animation! (You might need to think about how silly that seems).
.
If you need to access graphics-heavy applications over RDP, you may want to look at Ericom Blaze, a software product that accelerates AND compresses standard Microsoft RDP, so it speeds RDP while conserving bandwidth. Blaze accelerates RDP performance by as much as 10-25 times, and helps deliver higher frame rates and reduce screen freezes and choppiness.
You can read more about Blaze and download a free evaluation at:
http://www.ericom.com/ericom_blaze.asp?URL_ID=708
Adam