Here are the runtimes of our latest build for a variety of different scans, processed on a three different computers.
...
A
High-Performance computer
...
B
3D Workstation
...
C
Desktop
...
(Strange love)
...
NVidia RTX A5000
...
Spec to go here
The processing times, once photogrammetry has completed are as follows
...
Time
...
Asset
...
Images = C x L
...
Megapixel
...
UV Res
...
PC Class
...
1hr 20
...
66572fcb91bff8377800a4da
The FIRST run of this was 1K
...
x = x = 1
...
12.5 MP
...
1024
...
A
...
8hr 50
...
x = x = 1
...
12.5 MP
...
8192
...
A
...
12hr 15
...
664cbe8791bff832e000e2c0
...
x = x = 1
...
Rigsters
...
2048
...
A
...
4hr 00
...
66528f512e69c7e5d8006628
...
x = x = 4
...
scanologics
...
4096
...
HAL
...
24hr 30
...
Dinosaur
...
1392 = 348 x 4
...
60 MP
...
8192
...
B
...
1hr 40
...
x = x = 4
...
Chirs C
...
1024
...
B
...
21hr 45
...
6651fecc91bff83ce4007bc3
Second Run at 8K
...
x = x = 4
...
Chirs C
...
8192
...
A
...
22hr 45
...
6652887791bff83ce400da74
...
x = x = 1
...
Rigsters
...
8192
...
Benchmark system specifications:
OS: Windows Server 2019
CPU: AMD EPYC 32 Core
GPU: RTX A5000 24GB
Storage bandwidth: 3135 MB/s
Subject details | Total Time (hours : minutes) |
|---|---|
Dinosaur 61MP - Sony 1392 images in scan 8k texture | TBC |
Test Object 24MP - Nikon 1696 images in scan 4k texture | TBC |
Wonderboom 12MP - Samsung 589 images in scan 1k texture | TBC |