- - 5.1 Installing TurboVNC on Linux + 5.1 Installing TurboVNC on Linux
- - 5.2 Installing the TurboVNC Viewer on OS + 5.2 Installing the TurboVNC Viewer on OS X
- - 5.3 Installing the TurboVNC Viewer on + 5.3 Installing the TurboVNC Viewer on Windows
- - 5.4 Installing TurboVNC from Source + 5.4 Installing TurboVNC from Source
- - 5.5 Uninstalling TurboVNC + 5.5 Uninstalling TurboVNC
- - 6.1 Starting and Connecting to a + 6.1 Starting and Connecting to a TurboVNC Session
- - 6.2 Disconnecting and Killing a TurboVNC + 6.2 Disconnecting and Killing a TurboVNC Session
- - 6.3 Using TurboVNC in a Web Browser + 6.3 Using TurboVNC in a Web Browser
- - 6.4 Securing a TurboVNC Connection + 6.4 Securing a TurboVNC Connection
- - 6.5 Further Reading + 6.5 Further Reading
- - 7.1 Interframe Comparison + 7.1 Interframe Comparison
- - 7.2 Advanced Compression Options + 7.2 Advanced Compression Options
- - 7.3 Lossless Refresh + 7.3 Lossless Refresh
- - 7.4 Automatic Lossless Refresh + 7.4 Automatic Lossless Refresh
- - 7.5 Multithreading + 7.5 Multithreading
- - 7.6 Accelerating the Java TurboVNC + 7.6 Accelerating the Java TurboVNC Viewer
1 Legal Information
This document and all associated illustrations are licensed under the
-Creative
+Creative
Commons Attribution 2.5 License. Any
works that contain material derived from this document must cite The
VirtualGL Project as the source of the material and list the current URL
@@ -193,7 +193,7 @@ 1 Legal Information
part on the work of the Independent JPEG Group.
The TurboVNC Windows packages include -PuTTY, +PuTTY, which is released under this license.
@@ -227,9 +227,9 @@3 Overview
TurboVNC is a derivative of VNC (Virtual Network Computing) that is tuned to provide peak performance for 3D and video workloads. TurboVNC was originally based on the -TightVNC +TightVNC 1.3.x and -xf4vnc +xf4vnc code bases, and on the surface, it behaves similarly to its parents. However, TurboVNC compresses 3D and video workloads significantly better than the “tightest” compression mode in TightVNC 1.3.x while @@ -278,7 +278,7 @@
3 Overview
against a variety of captured RFB sessions that simulate real-world application workloads, both 2D and 3D. For more information on the research leading to TurboVNC’s encoder design, see -this +this report.In addition to high performance, other notable features of TurboVNC @@ -381,7 +381,7 @@
4.1 Linux/x86 and Other x86 Un*x Operating Systems
Font Dependencies
Installing TurboVNC
-
-
- +
-
Download the appropriate TurboVNC binary package for your system from
the
- Files
+ Files
area of the
- TurboVNC
+ TurboVNC
SourceForge project page. Packages are
provided for RPM-based and Debian-based Linux distributions that contain
GLIBC 2.3.4 or later (including
- Fedora
+ Fedora
4 or later,
- Red
+ Red
Hat Enterprise
- Linux/CentOS
+ Linux/CentOS
4 or later,
- SuSE
+ SuSE
Linux
- Enterprise/openSUSE
+ Enterprise/openSUSE
10 or later, and
- Ubuntu
+ Ubuntu
6.06 or later.)
- - +
-
Log in as root, cd to the directory where you downloaded the binary
package, and issue one of the following commands:
-
@@ -532,9 +532,9 @@
5.2 Installing the TurboVNC Viewer on OS X
Download the TurboVNC Mac disk image (TurboVNC-{version}.dmg) from the - Files + Files area of the - TurboVNC + TurboVNC SourceForge project page. -
@@ -554,9 +554,9 @@
5.3 Installing the TurboVNC Viewer on Windows
for 32-bit systems orTurboVNC64-{version}.exefor 64-bit systems) from the - Files + Files area of the - TurboVNC + TurboVNC SourceForge project page. -
@@ -575,9 +575,9 @@
5.4 Installing TurboVNC from Source
download the TurboVNC source tarball (turbovnc-{version}.tar.gz) from the -Files +Files area of the -TurboVNC +TurboVNC SourceForge project page, uncompress it,cd turbovnc-{version}, and readBUILDING.txtfor further instructions on how to build @@ -1194,22 +1194,30 @@7.1 Interframe Comparison
and over again, and this can cause redundant framebuffer updates to be sent to the VNC viewer. The TurboVNC Server can guard against this by maintaining a copy of the remote framebuffer for each connected viewer, -comparing each new framebuffer update against the pixels in the -framebuffer copy, and discarding any redundant updates before they are -sent to the viewer. +comparing each new framebuffer update rectangle against the pixels in +the framebuffer copy, and discarding any redundant rectangles before +they are sent to the viewer. -Enabling interframe comparison increases the memory usage of the +
Interframe comparison has some tradeoffs associated with it. Perhaps +the most important of these is that it increases the memory usage of the TurboVNC Server by a factor of N, where N is the number of connected -clients, and interframe comparison increases the server CPU usage by -about 10-15% as well. Further, duplicate framebuffer updates are not -typically a problem for 3D and video applications, and the effects of -these duplicate updates, even when they exist, are not typically -noticeable on high-speed networks. Thus, interframe comparison is not -enabled by default and should not generally be enabled except on -low-bandwidth networks and with applications for which it can be shown -to be beneficial.
- -Interframe comparison can be enabled by either passing an argument of +clients. This can prove to be quite significant if the remote desktop +size is relatively large.
+ +2D applications are most often the ones that generate duplicate +framebuffer updates, so using interframe comparison with such +applications can significantly reduce the network usage and the server +CPU usage (since fewer rectangles are actually being encoded.) However, +with 3D applications, interframe comparison increases server CPU usage +without providing any significant reduction in network usage. +Furthermore, the effects of duplicate framebuffer updates are not +typically noticeable on high-speed networks, but an increase in server +CPU usage might be.
+ +For these reasons, interframe comparison is not enabled by default and +should not generally be enabled except on low-bandwidth networks and +with applications for which it can be shown to be beneficial. +Interframe comparison can be enabled by either passing an argument of
@@ -1560,7 +1568,7 @@-interframetovncserverwhen starting a TurboVNC Server session or by requesting a compression level of 5 or higher from the viewer (see below.)Java Web Start
client machine. This mechanism is preferred over deploying the viewer as an applet, since JPEG decoding cannot be accelerated when the Java TurboVNC Viewer is run as an applet. See -http://www.TurboVNC.org/Documentation/JWS +http://www.TurboVNC.org/Documentation/JWS for more details.
@@ -1926,7 +1934,7 @@10 Compatibility Guide
In order to realize the full performance benefits of TurboVNC, it is necessary to use a TurboVNC server and a TurboVNC viewer in concert. However, TurboVNC is fully compatible with -TigerVNC, +TigerVNC, TightVNC, RealVNC, and other VNC flavors. You can use the TurboVNC Viewer to connect to a non-TurboVNC server (or vice versa), although this will generally result in some decrease in performance.
@@ -2287,9 +2295,9 @@11.1 Server Settings
If interframe comparison is enabled (see Section 7.1), then setting this environment variable to 1 will cause the interframe comparison engine - (ICE) to change the color of duplicate updates without culling them from - the update stream. This allows you to easily see which applications are - generating duplicate updates. + (ICE) to change the color of duplicate screen regions without culling + them from the update stream. This allows you to easily see which + applications are generating duplicate updates. diff --git a/doc/performance.txt b/doc/performance.txt index 43280b9be..d843e6098 100644 --- a/doc/performance.txt +++ b/doc/performance.txt @@ -123,22 +123,29 @@ Certain ill-behaved applications can sometimes draw the same thing over and over again, and this can cause redundant framebuffer updates to be sent to the VNC viewer. The TurboVNC Server can guard against this by maintaining a copy of the remote framebuffer for each connected viewer, comparing each new -framebuffer update against the pixels in the framebuffer copy, and -discarding any redundant updates before they are sent to the viewer. - -Enabling interframe comparison increases the memory usage of the TurboVNC -Server by a factor of N, where N is the number of connected clients, and -interframe comparison increases the server CPU usage by about 10-15% as well. -Further, duplicate framebuffer updates are not typically a problem for 3D and -video applications, and the effects of these duplicate updates, even when they -exist, are not typically noticeable on high-speed networks. Thus, interframe -comparison is not enabled by default and should not generally be enabled except -on low-bandwidth networks and with applications for which it can be shown to be -beneficial. - -Interframe comparison can be enabled by either passing an argument of -''-interframe'' to ''vncserver'' when starting a TurboVNC Server session or by -requesting a compression level of 5 or higher from the viewer (see below.) +framebuffer update rectangle against the pixels in the framebuffer copy, and +discarding any redundant rectangles before they are sent to the viewer. + +Interframe comparison has some tradeoffs associated with it. Perhaps the most +important of these is that it increases the memory usage of the TurboVNC Server +by a factor of N, where N is the number of connected clients. This can prove +to be quite significant if the remote desktop size is relatively large. + +2D applications are most often the ones that generate duplicate framebuffer +updates, so using interframe comparison with such applications can +significantly reduce the network usage and the server CPU usage (since fewer +rectangles are actually being encoded.) However, with 3D applications, +interframe comparison increases server CPU usage without providing any +significant reduction in network usage. Furthermore, the effects of duplicate +framebuffer updates are not typically noticeable on high-speed networks, but an +increase in server CPU usage might be. + +For these reasons, interframe comparison is not enabled by default and should +not generally be enabled except on low-bandwidth networks and with applications +for which it can be shown to be beneficial. Interframe comparison can be +enabled by either passing an argument of ''-interframe'' to ''vncserver'' when +starting a TurboVNC Server session or by requesting a compression level of 5 or +higher from the viewer (see below.) ** Advanced Compression Options {anchor: AdvancedCompression}