Agisoft Metashape
Agisoft Metashape => Bug Reports => Topic started by: andyroo on March 12, 2021, 02:25:09 AM
-
Win10 w/ Threadripper 3960X ( and two RTX 1080 Super GPUs and 256GB RAM (85% free)
I'm aligning ~36000 images in one chunk and trying to figure out why metashape is being super unresponsive and barely using any resources (1 core). When trying to check where the process is, I found that the screen has not updated for about 6 hours (08:41:11 local time and it's 15:22 right now), and the logfile is being written very slowly (currently 44h behind at 11:07:23).
logfile is writing to a SSD with 500GB of space. I thought it might be too big (77MB) so I copied & cleared it but write speed didn't change.
Resource Monitor shows 7 root threads waiting for a child thread, and 358 associated handles, which I'm happy to provide if they'd be useful
the last line showing in the console (which is currently unresponsive) is bolded and underlined below. The logfile lines being written look like it's in the same process:
2021-03-11 08:41:09 block_obs: 25.066 MB (25.066 MB allocated)
2021-03-11 08:41:09 block_ofs: 2.5294 MB (2.5294 MB allocated)
2021-03-11 08:41:09 block_fre: 0 MB (0 MB allocated)
2021-03-11 08:41:10 adding 331032 points, 0 far (13.1678 threshold), 2 inaccurate, 2 invisible, 0 weak
2021-03-11 08:41:10 adjusting: xxx 0.694264 -> 0.287228
2021-03-11 08:41:10 adding 6 points, 2 far (13.1678 threshold), 2 inaccurate, 2 invisible, 0 weak
2021-03-11 08:41:10 optimized in 0.873 seconds
2021-03-11 08:41:10 f 8863.4, cx 27.5, cy -1.32353, k1 -0.072948, k2 0.0864567, k3 -0.0213253
2021-03-11 08:41:10 f 8862.78, cx 27.5, cy -1.32353, k1 -0.0729651, k2 0.086042, k3 -0.0230285
2021-03-11 08:41:10 f 8863.4, cx 27.5, cy -1.32353, k1 -0.072312, k2 0.0833413, k3 -0.0185212
2021-03-11 08:41:11 adjusting: xxxx 0.295707 -> 0.287377
2021-03-11 08:41:12 loaded projections in 0.003 sec
2021-03-11 08:41:12 tracks initialized in 0.072 sec
2021-03-11 08:41:12 adding 331034 points, 0 far (13.1678 threshold), 1 inaccurate, 3 invisible, 0 weak
2021-03-11 08:41:12 block: 1 sensors, 28 cameras, 106716 points, 0 projections
2021-03-11 08:41:12 block_sensors: 0.000816345 MB (0.000816345 MB allocated)
2021-03-11 08:41:12 block_cameras: 0.0108948 MB (0.0108948 MB allocated)
2021-03-11 08:41:12 block_points: 4.88507 MB (4.88507 MB allocated)
2021-03-11 08:41:12 block_tracks: 0.407089 MB (0.407089 MB allocated)
2021-03-11 08:41:12 block_obs: 0 MB (0 MB allocated)
2021-03-11 08:41:12 block_ofs: 0 MB (0 MB allocated)
2021-03-11 08:41:12 block_fre: 0 MB (0 MB allocated)
2021-03-11 08:41:12 block: 2 sensors, 47 cameras, 192836 points, 0 projections
2021-03-11 08:41:12 block_sensors: 0.00163269 MB (0.00163269 MB allocated)
2021-03-11 08:41:12 block_cameras: 0.0182877 MB (0.0182877 MB allocated)
2021-03-11 08:41:12 block_points: 8.82733 MB (8.82733 MB allocated)
2021-03-11 08:41:12 block_tracks: 0.735611 MB (0.735611 MB allocated)
2021-03-11 08:41:12 block_obs: 0 MB (0 MB allocated)
2021-03-11 08:41:12 block_ofs: 0 MB (0 MB allocated)
2021-03-11 08:41:12 block_fre: 0 MB (0 MB allocated)
-
Hello andyroo,
Do you have "fine-level task subdivision" enabled and whether the project is saved in PSX format?
Please also check, if the disk swap has been used.
-
Fine level task subdivision is enabled. Max RAM usage was around 30-40GB out of 256GB so disk swap shouldn't have been used, but I didn't exhaustively check with powershell or Perfmon. If it would help, I can run again and try that.