topic Re: "otimizing" Why is this still so slow. in ReCap Forum

"otimizing" Why is this still so slow.

arron.craig — Sun, 29 Nov 2020 19:24:40 GMT

I've been waiting for a project to optimize for 3 days now. Based on previous larger projects I expected this to take about 12 hours so I started it on a Friday. I cannot fathom why this is taking so long.

The project is only 32 scans, 55GB and is from an RTC360. I deleted a little bit of noisey data, probably about 5% of the scan and then saved (not saved as), choosing to optimize.

It's only using 13GB of ram and 8% CPU (sparodic usage on 4 cores) and 8% GPU, no disk activity.

Recap Pro 2021 (cant confirm version while it's stuck optizing)

Intel Core i9 10900K

64GB DDR4 3200 RAM

Samsung 2tb NVMe

Nvidia RTX 2070 SUPER

Has anyone seen it take this long? Am i best off killing it and starting again?

Re: "otimizing" Why is this still so slow.

yan.fu — Mon, 30 Nov 2020 18:36:00 GMT

Could you check if files are kept written into your temp folder to see if it is still running of or might just hang there?

C:\Users\<USERNAME>\AppData\Local\Autodesk\Autodesk ReCap\import_output

Re: "otimizing" Why is this still so slow.

arron.craig — Mon, 30 Nov 2020 18:41:22 GMT

Hi @yan.fu, I just got into the office and it has now finished, ended up taking just over 4 days. The project file has reduced from 55GB to 53GB....

There are no files for this project in import_output (just some old files from March)

Is this long run time expected behaviour?

Re: "otimizing" Why is this still so slow.

arron.craig — Sun, 06 Dec 2020 18:51:09 GMT

@yan.fu Is the long run time like this expected behaviour?

Re: "otimizing" Why is this still so slow.

yan.fu — Mon, 07 Dec 2020 01:45:10 GMT

Hi @arron.craig ,

It depends on the area of the deleted points and how complicate the selections are.

Also, because there are a lot of I/O to the disk so the performance of the drive also matters.

Yan

Re: "otimizing" Why is this still so slow.

arron.craig — Mon, 07 Dec 2020 02:07:04 GMT

@yan.fu As per my original post, I am not getting any measurable I/O on the disk, it's usage sits around 0%-1% while "optimizing".

It's an NVME drive with 3000MB/S read/write and is a seperate drive to the OS.

I deleted about 2GB worth of points via very simple rectangular selection.

Re: "otimizing" Why is this still so slow.

yan.fu — Mon, 07 Dec 2020 02:11:52 GMT

Thank you for your information. We will do some investigation from our side for the case you mentioned.

Thanks,

Yan

Re: "otimizing" Why is this still so slow.

Les_Gustin — Mon, 07 Dec 2020 16:29:33 GMT

I am having similar issues. I Created multiple regions with no performance issues in the file until optimization is run. Once Optimization is finished regen and movement around the point cloud is very slow. This also translates to the Revit file it is linked in.

Re: "otimizing" Why is this still so slow.

arron.craig — Mon, 07 Dec 2020 18:54:46 GMT

Performance after optimising for me is no different, How long did optimising take you though?

Re: "otimizing" Why is this still so slow.

Les_Gustin — Mon, 07 Dec 2020 20:30:46 GMT

It is a 35 scan point cloud that has been cropped and consolidated to a single recap scan. The regions were created after consolidation. While no where near your time frame. It took 15mins to Optimize the 1.8 Gb point cloud with 4 very small Regions with no change in file size afterwards but the point cloud performance was unusable after optimization.

i9-9920x

64 GB of Ram

Quadro RTX 4000

WD Black SN750 NVMe