<%NOJS_WARNING%>

KISTERS Logo KISTERS logo

Navigation :  

> 3DVS WebViewer > Pas de chapitre par ce niveau

Configuration requise

Scroll PDF

3DViewStation WebViewer


To determine a realistic average RAM and VRAM (main memory and GPU memory) consumption, the native CAD data must first be converted into the proprietary 3DVS format. After conversion, several representative models (small, medium, and large) should be loaded into the 3DViewStation WebViewer or Desktop, and the corresponding average resource consumption values should be recorded.

Evaluating RAM / VRAM consumption using the Process Explorer:

Download the Process Explorer software (https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer)

Load the 3DVS test file(s) into the 3DViewStation WebViewer or Desktop

Open the Process Explorer

Locate CRendererInstance.exe (or 3DViewStation.exe) in the Process Explorer Process list

Right-click on CRendererInstance.exe (or 3DViewStation.exe) and select Properties... from the context menu

Select the Performance tab and get the value of Virtual Memory > Private Bytes

Select the GPU Graph tab and get the value of Dedicated GPU Memory

Hardware sizing examples based on a standard server configuration for a maximum of 20 concurrent viewing sessions

The following examples illustrate the estimated hardware requirements based on measured resource consumption.

Standard Server Assumption (All calculations below assume a standard server configuration):

256 GB RAM

1 GPU with 24 GB VRAM

If the calculated requirements exceed the capacity of a single server, multiple servers or additional GPUs are required. Load sharing between multiple servers, or servers with multiple graphics cards are supported.

Testfile size (3DVS)

Consumed RAM (Private Bytes)

Consumed VRAM (Dedicated GPU Memory)

RAM needed for 20 sessions

VRAM needed for 20 sessions

Server requirements

Verdict

65 MB

625 MB

307 MB

625 MB × 20 = 12,500 MB ≈ 16 GB

307 MB × 20 = 6,140 MB ≈ 8 GB

Required RAM: 16 GB → fits into 256 GB

Required VRAM: 8 GB → fits into 24 GB

Standard Server sufficient

500 MB

4808 MB

2361 MB

4,808 MB × 20 = 96,160 MB ≈ 96 GB

2,361 MB × 20 = 47,220 MB ≈ 48 GB

Required RAM: 96 GB → fits into 256 GB

Required VRAM: 48 GB → exceeds 24 GB

A single GPU is not sufficient:

1 server with 2 GPUs (24 GB VRAM each)

OR

2 standard servers, each with 1 GPU

1000 MB

9615 MB

4723 MB

9,615 MB × 20 = 192,300 MB ≈ 192 GB

4,723 MB × 20 = 94,460 MB ≈ 96 GB

Required RAM: 192 GB → fits into 256 GB, but with limited reserve

Required VRAM: 96 GB → requires multiple GPUs

Multiple GPUs and potentially multiple servers are required:

1 server with 4 GPUs (24 GB VRAM each)

OR

2 standard servers, each with 2 GPUs

OR

4 standard servers, each with 1 GPU

For production environments, we recommend including at least a 30–50% resource reserve to account for:

Operating system overhead

Background processes

Peak loads

Future scaling

If larger files or a higher number of parallel sessions are expected, plan additional servers or GPUs accordingly.


Minimal system requirements

Windows 10 (1607) (x64) / Server 2016 (1607) (x64) and newer

Processor with SSE 4 support

> 4 GB RAM1

3 GB hard drive space (does not include space for models)

Dedicated graphics card with DirectX 11 or better1

Recommendation:

Dedicated server with a GPU and DirectX 12-compatible driver is recommended for best performance

Virtual machines are allowed (in this case, GPU passthrough is recommended; vGPU is supported)

CPU rendering is possible (recommended for 2D only)

1 Hardware recommendations depend heavily on the models being visualized.

License server

Minimal system requirements

Windows 10 (x64) / Server 2016 (x64) and newer2

200 MB hard drive space

Virtual machine allowed

2 The requirements for the license service are fulfilled with the requirements of the operating system.

English Version German Version Japanese Version Italian Version French Version Spanish Version Chinese Version Tutorial File Format list-PDF Admin-PDF Release Notes-PDF Function list-PDF

Editorial - Protection des données