System Requirements
Since loading and optimizing complex and heavy CAD files requires a lot of computing power, you should use Pixyz with the best hardware configuration possible (powerful CPU-GPU, confortable quantity of RAM). Please note that system requirements heavily depend on the type and complexity of CAD and 3D assets your company or studio is dealing with (eg: a game character vs. a complete oil and gas platform)
One instance of Pixyz is multi-threaded (up to 32-threads per Pixyz task)
1 CPU with 4 to 32 CPU cores is recommended. Ideal configuration is 8-12 core per Pixyz task (can be configured within Pixyz settings (see Preferences))
Memory usage depends on the volume of data that Pixyz will deal with during the task
It is not easily predictable but for simplification matters, the number of polygons in your scene will be the major indicator of memory consumption. We recommend sizing a comfortable amount of RAM in order to prevent Pixyz from exiting during the process due to lack of memory.
As a reference, 1M polygons takes about 0.5Gb of RAM and a point cloud of 1M points takes about 50Mb of RAM
Find below the recommended and minimum system configurations to run Pixyz efficiently:
Recommended
- Processor: Intel Core i7 3.0 GHz or higher
- RAM: 16 GB or more
- Graphics Hardware: nVidia GeForce RTX 3080
- Disk Space: 1 GB or more (with dynamic swap)
- Operating System: Windows 10 and 11 64-bit, Linux Ubuntu/Debian, Docker, Windows Server 2019/2022.
Minimum
- Processor: x64 dual-core 2GHz
- RAM: 4 GB
- Graphics Hardware: OpenGL 4 compatible
- Disk Space: 200 MB
- Operating System: Windows 10 and 11 64-bit, Linux Ubuntu/Debian, Docker, Windows Server 2019/2022.
About GPU
Warning
AMD graphic cards are not fully supported, using one might result in a poor experience of Pixyz GPU-based features. We recommend using nVidia graphic cards.
A few Pixyz algorithms are accelerated on GPU (ray-casting-based algorithms). If there is no GPU on the machine, your Pixyz integration will fail on using GPU-accelerated capabilities. This will activate the CPU fallback for any ray-casting algorithm which can lead to significant performance reduction (up to 100x slower than with a GPU).
For information, GPU-acceleration can be turned off using the following Pixyz API command:
core.setModuleProperty("Algo", "DisableGPUAlgorithms", "True")
List of GPU-accelerated functions in Pixyz Scenario Processor
algo.createvisibilityinformation
algo.createVisibilityInformationFromViewPoints
scene.getHiddenPartOccurrences
algo.removeOccludedGeometries - delete parts, patches or polygons not viewed from a sphere around the scene
algo.removeOccludedGeometriesAdvanced - delete parts, patches or polygons not viewed from a set of cameras automatically generated
algo.removeOccludedGeometriesFromPoints
algo.removeOccludedGeometriesFromViewPoints
algo.findOccludedPartOccurrences
algo.findOccludedPartOccurrencesAdvanced
algo.createVisibilityInformationAdvanced
algo.orientPolygonFacesAdvanced
Along with all render functions relying on the Vulkan capabilities of Pixyz.
Activating GPU acceleration in Docker image
The following link contains instructions to setup nVidia drivers and nVidia-Docker modules for Docker images: https://github.com/NVIDIA/nvidia-docker/wiki/Installation-(Native-GPU-Support)#prerequisites
Related topics
- Application Installation
- System Requirements for Unity (article by Unity)