badam wrote: ↑Sun Sep 24, 2023 8:30 am
Can you attach the log files for the import?
Or something like that. But those times are not exceptional, i usually get around the same with single threaded with a 5600G without dedicated gpu. Maybe can we share a dataset to compare the two setups (everything on nas, and low budget vs highest budget local storage)
I'm hesitant to share those log files as they do contain various IP addresses, EID info, and Product Key info.
For simple datasets where the majority of the scans are of large planar sufaces and there are no parallaxing issues with the scanner imagery being setup close to objects, these are some of the times it takes to import. (Both of these datasets were included in the original testing within the "Project 1 - Outdoor/Simple")
When the imagery captured has lots of parallaxing issues to deal with, it has been typical for those imports to take considerably longer. While my laptop will import most scans at 1m to 1m15s per setup, those setups that deal with parallaxing have always been anywhere from 2 to 5 minutes/setup.
On our dedicated desktops that run a 13900K setup with proper cooling and power supply will cut that import time almost in half. For the setups with parallaxing issues, they generally never take more than 1.5 to 2 minutes/setup compared to my laptop's 2 to 5 minutes.
The import is still very much a CPU intensive operation, but lately I've been noticing my GPU getting hit more and more. Still nothing too crazy at this time that'll make a massive difference after seeing the latest results, but still intersting none the less.
You do not have the required permissions to view the files attached to this post.