Register 360 2023.0.3 using GPU for Import Now???

[smacl]

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)

My guess is that while 70W+ TDP average / max ~100W on the 12950HX is very good for that chip (base TDP is 55W), this is still a long way off a decent desktop CPU, e.g. i9 13900K is 125W base / 250w turbo). AFAIK, laptops and NUCs tend to thermal throttle pretty quickly on all core loads and the clock rate drops back significantly as a result. If you look at this in action on the likes of task manager, it still shows 100% CPU usage but you'll notice the clock speed drops off massively as you lose turbo due to thermals. In a small package, GPU and CPU tend to heat each other up which doesn't help. The 12900hx is better than the 5600G on paper, but guessing your 5600G is a desktop build with the advantages that that entails.

@Kruse, great work once again on the benchmarking. The improvements between versions seem pretty minor in this case.

[Kruse]

Can you attach the log files for the import?
%programdata%/Leica geosystems/register360/...
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")

Import times for Medium density scans both indoor and outdoor.png

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.

[Kruse]

I ran another test on the 2023.0.3 version of Reg360+ with 40 High Density RTC 360 scans and imported them without images (just B/W & Intensity) and they imported on the same computer/drives at 21 minutes 36 seconds (from logs) or ~32.4 seconds per setup. These 40 scans contained 3.03 Billion points after import and the project database was 68GB.

Like before, the CPU quickly was maxed out due to thermals. Importing just B/W scans would continuously utilize my dedicated GPU and hit similar wattages used as the first tests. So when importing images, it doesn't seem like Reg360+ is using the GPU a whole lot to process those, if at all. The GPU is mostly used for some kind of background processing of the point clouds. No clue what it could be though.

CPU clock speeds at idle before import:

B_W Import - CPU Idle Clock Speeds Before Import.pdf

CPU clock speeds when fully boosted and not thermal throttled yed:

B_W Import - CPU Boost Clock Speeds At Start of Import.pdf

CPU clock speeds when thermal throttled:

B_W Import - CPU Clock Speeds and CPU Temps when Thermal Throttled.pdf

GPU Usage during import of B/W scans and the thermal throttle clock speeds of the CPU mid import:

B_W Import - GPU Usage and CPU Thermal Throttle Clock Speeds Mid Import.pdf

Final CPU Usage Results:

B_W Import - CPU Usage Results.pdf

Final GPU Usage Results:

B_W Import - GPU Usage REsults.pdf

Final NVMe Usage Results:

B_W Import - NVMe Usage Results.pdf

[smacl]

Really interesting information, I'm surprised the average thermal throttled temperature was 98c, I'd have expected lower. Not sure either of my i9 NUCs would sustain that for an extended time frame.

[Kruse]

Really interesting information, I'm surprised the average thermal throttled temperature was 98c, I'd have expected lower. Not sure either of my i9 NUCs would sustain that for an extended time frame.

yeah, it pushes some heat out the back when importing raw scans lol. The cooling on this Generation of Dell Precision laptop probably isn't the best, but the cooling definitely won't get any better unless I set it up next to an AC vent, .