Remote Visualization (RV) describes the process of rendering images in real-time based on data, which is not stored locally on the system where you are observing the rendering with the possibility of interaction. To achieve this, two different approaches are common. The first approach is remote computation, where the data is kept remotely but the rendering is performed locally. The second approach is the actual remote visualization, where data and rendering are performed remotely and the images are transmitted afterwards to the local system.

Requirements and Use Cases

No special requirements are needed on the local system, but accounts to the remote systems of either Linux Cluster or SuperMUC are required. For some systems/work flows, a VNC client is required (TigerVNC (consider maybe the stand-alone clients for testing), RealVNC, TightVNC).

Typical use cases for RV comprise post-processing and handling of large data sets in the location where they were generated, e.g on the LRZ HPC clusters. Usage of licensed software with no permission to install it on local machines, or having no local access to license servers.


The network connection quality in terms of transmission bandwidth and latency - also geographical distance - might affect the RV image quality and the ability to smoothly interact with the graphics visualization. Furthermore, the RV system at the LRZ represents a limited resource which is shared by many users. An immediate availability cannot be granted.

Visualization Hardware

Important notice: The RVS Systems are only accessible for users of the Linux Cluster (Bavarian Universities) and NOT for SuperMUC-NG Users. There will be another remote visualization system for SuperMUC-NG Users coming in 2020/2021.

SystemRVS subsystemOSGPUs/NodeCores/NodeMemory/NodeSubmit RV job viaSubmit Command
Linux Clusterrvs1, ..., rvs7SLES 12NVidia TeslaK20Xm16 (SandyBridge)128 GBlxlogin*.lrz.demodule: rvsvnc

Depending on the Operating System (OS), different software stacks are present.
The 480 GB of memory in parentheses on SuperMUC Phase 2 are the effectively usable memory. The rest is reserved for the system.