Author Topic: Dense Cloud Build - exponential time increase  (Read 4787 times)

David Cockey

  • Full Member
  • ***
  • Posts: 209
    • View Profile
Dense Cloud Build - exponential time increase
« on: July 23, 2014, 06:08:14 AM »
Times for "filtering depth maps" during Build Dense Cloud appear to increase exponentially with the number of cameras used on my current project. Is this normal and expected? I don't recall encountering it before.  Attached is log file for a batch run with three chunks using 361, 402 and 502 cameras. (File edited to reduce size so it could be uploaded) Times for "filtering depth maps" were 626 sec, 2332 sec and 4484 sec.

PhotoScan Standard Edition Version 1.0.4 build 1847 (64 bit)
Windows 8.1
i7-3770 CPU, 4 core and 8 virtual threads, virtually 100% use of CPU during "filtering depth maps"
AMD 7770 GPU, not used during "filtering depth maps"
16GB memory, 8.4GB maximum used during run.

GPU is used during "depth reconstruction".


  • Sr. Member
  • ****
  • Posts: 284
    • View Profile
Re: Dense Cloud Build - exponential time increase
« Reply #1 on: August 16, 2014, 02:08:05 PM »
Depth maps are filtered against other cameras so the more cameras you have the higher your processing time will be (exponentially). My assumption only.