| 33 | | VNC follows a very general approach, where a remote graphical desktop on one node of the remote cluster is started. \\ |
| 34 | | On the user's workstation only a lightweight VNC viewer has to be installed. \\ |
| 35 | | The graphical screen of the remote desktop is send as an image from the cluster to the viewer on the fly. |
| 36 | | |
| 37 | | The user can work with this remote graphical desktop in the usual way, just by interacting with keyboard and mouse. \\ |
| 38 | | This is a very convenient way to work on a remote machine, not only for data visualization. |
| 39 | | |
| 40 | | VNC offers the ability to detach from a session (running in a VNC server) and then attach back at a later time. \\ |
| 41 | | That means, that the user can close the VNC viewer on his/her computer and any application started in the VNC session on the server keeps on running - they do not pause or even be killed. \\ |
| 42 | | Later on the user can connect back to the same VNC session (even from a different computer) and keep on working. \\ |
| 43 | | |
| 44 | | [[Image(Trac_Setup_VNC.png, 640px)]]\\ |
| 45 | | |
| 46 | | ==== hardware accelerated rendering (OpenGL) |
| 47 | | [[Image(https://upload.wikimedia.org/wikipedia/commons/thumb/6/67/X11transport.png/600px-X11transport.png, 200px, align=right, margin=0)]] |
| 48 | | Whenever an OpenGL capable visualization software, like !VisIt, is started on the remote cluster node, \\ |
| 49 | | OpenGL commands can be redirected to the GPU of this node with the help of [http://www.virtualgl.org VirtualGL]. \\ |
| 50 | | * ... using '''vglrun''' (e.g. vglrun paraview) |
| 51 | | This way the hardware accelerated rendering capabilities of a cluster node (if available) can be exploit for remote rendering. \\ |
| 52 | | (attention: __without__ VirtualGL software, rendering using the CPU instead of the GPU must be used (if available), which is much slower). |
| 53 | | |
| | 33 | \\ |
| 95 | | == Use hardware acceleration in your VNC session |
| | 77 | VNC follows a very general approach, where a remote graphical desktop on one node of the remote cluster is started. \\ |
| | 78 | On the user's workstation only a lightweight VNC viewer has to be installed. \\ |
| | 79 | The graphical screen of the remote desktop is send as an image from the cluster to the viewer on the fly. |
| | 80 | |
| | 81 | The user can work with this remote graphical desktop in the usual way, just by interacting with keyboard and mouse. \\ |
| | 82 | This is a very convenient way to work on a remote machine, not only for data visualization. |
| | 83 | |
| | 84 | VNC offers the ability to detach from a session (running in a VNC server) and then attach back at a later time. \\ |
| | 85 | That means, that the user can close the VNC viewer on his/her computer and any application started in the VNC session on the server keeps on running - they do not pause or even be killed. \\ |
| | 86 | Later on the user can connect back to the same VNC session (even from a different computer) and keep on working. \\ |
| | 87 | |
| | 88 | [[Image(Trac_Setup_VNC.png, 380px)]]\\ |
| | 89 | |
| | 90 | ==== hardware accelerated rendering (OpenGL) |
| | 91 | [[Image(https://upload.wikimedia.org/wikipedia/commons/thumb/6/67/X11transport.png/600px-X11transport.png, 200px, align=right, margin=0)]] |
| | 92 | Whenever an OpenGL capable visualization software, like !VisIt, is started on the remote cluster node, \\ |
| | 93 | OpenGL commands can be redirected to the GPU of this node with the help of [http://www.virtualgl.org VirtualGL]. \\ |
| | 94 | * ... using '''vglrun''' (e.g. vglrun paraview) |
| | 95 | This way the hardware accelerated rendering capabilities of a cluster node (if available) can be exploit for remote rendering. \\ |
| | 96 | (attention: __without__ VirtualGL software, rendering using the CPU instead of the GPU must be used (if available), which is much slower). |
| | 97 | |
| | 98 | |
| | 99 | ==== Use hardware acceleration in your VNC session |
