The 3D SSR render server gets the volume data for the images to render via the TileServer interface and does not require direct access to the central image storage. This allows deployment of the render server outside the intranet and allows for the possibility to use mixed cloud/on-premises installations for this component.

Each 3D SSR render server can provide multiple render streams. Graphics Memory and power will be split. E.g. with an 8 GB graphics card you could either provide one stream with 8 GB possible volume load, or two streams with 4 GB possible volume load. This decision should be discussed with your account manager in preparation for deployment, and advisement can be provided based on expected use.

• Windows Server 2012/2016/2019
• VisionHub 1 GB; NodeJS 10 GB
• Local cache: X TB (depending on the number of images)
• Required for caching tiles before rendering. If the system is configured to provide a single stream with 8 GB of volume load, then each dataset might load up to 8 GB of image tiles from the VisionHub tile server. To avoid re-loading, we suggest choosing a cache size based on the number of images on the system. E.g. if there are 4 images and you have a 8 GB graphics card you would need 32 GB of cache; 500 images X 8 GB = 4 TB etc. The more images, the greater the cache volume needed.
• Another option is to use a high-speed central storage for cache, but this is only possible if installed in same intranet.