I introduced on the new Thin Wire compatibiltiy mode in 7.6 FP3 recently blogged and have some great feedback had
it's really satisfying to see a client, no matter how I do on efficient bandwidth and CPU usage, there are many reasons you might want a low-cost graphics protocol:
- battery life on mobile devices - both CPU and GPU usage drain batteries;
- more users on your existing hardware get;
- avoid expensive network upgrades;
- by improving high frame rates user experience;.
- avoid WiFi You pay for the bandwidth, 3G / 4G
Sometimes less is more
become While many applications! graphically in recent years more, many have not:
- have
- develops applications for mobile devices flatter and easier, much primary color blocks, in recognition that they are often used with tiny screens, will and limited to a bandwidth ;
- applications your average office workers are heavily used not graphically demanding - think about Microsoft Word, where a user typically is black text on white background enter;
- Bespoke legacy applications are indeed very simple interfaces with similar to a DOS / Unix shell, say.
Even if an application is graphically, sometimes you might not so rich graphical information (or want to pay for the bandwidth to transmit it).
Thin Wire compatibility 16-bit mode
Thin Wire compatibility mode implements an optional 16-bit graphics mode for bandwidth usage to reduce. Tests here at Citrix exhibit ~ 15-20% bandwidth reduction for typical "Office" type workloads. Unlike the legacy mode, so that 16-bit not affect application compatibility and, by setting the "Preferred color depth" (user) policies are configured to "16-bit". The quality degradation is barely perceptible
Lower Still - Experimental 8-bit mode
( Disclaimer: This is an experimental.! function and is not supported by Citrix, it is provided for evaluation purposes feedback is to ask about possible new functions and are only used in a test environment and not in production environments.)
I should add be an experimental 8-bit setting for ultra-low bandwidth utilization. To enable this, add the following registry value to the VDA, where you use 8-bit:
[REG_DWORD] HKLM Software Citrix Graphics LowBandwidthMode
- this registry value to force "2" is an 8-bit session.
- to force this registry value to "1" 16-bit, although the "Preferred use should be done, color depth" policy.
Once set, all connections to the VDA are displayed in 8-bit color. At the moment we have the only tested with Linux and Windows endpoints - feedback on other devices would be welcome
How not affected in 16-bit mode, the application compatibility is !. However, photographic images are naturally somewhat degraded appear - is 8-bit really designed for simple workloads, where it offers a perfectly acceptable experience especially when the bandwidth is an important consideration (for example, Office / web apps / etc.). We have seen up to 50% (!) In the reduced bandwidth compared with Thin Wire default compatibility mode out-of-the-box settings.
What to expect
First, here is a screen grave of a 24-bit session configured Thin Wire compatibility to use, is in the standard mode.
As you can see, the Windows 10 wallpaper and photo images within the browser are of high quality and you would be hard-pressed to tell the difference between a local and remote session to say
now, with the 16-bit policy enables .:
photo images in the browser looks very similar to the original 24-bit image, but are obviously some slopes in the Windows 10 wallpaper. Nevertheless quite acceptable
Finally, 8-bit .:
Any photographic image degraded, but it is still possible to pick out detail and is more important, Text and solid color areas remain largely intact.
Please have a game and let me know what you think!
More Contacts
Attention! Registry Editor incorrectly can cause serious problems that you might need to reinstall your operating system. Citrix can not guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
The above article includes a product configuration or method that Citrix not currently provide support for. Use of this configuration should only be used in a lab or test environment and not with production deployments. The author actively seeks feedback on the potential of the support for the implementation of this configuration, but the shape of each level of support will still be determined.
0 Komentar