Messages

1

General / Re: Ram usage on Orthomosiac stage

« on: July 05, 2018, 08:54:38 PM »

Fkybarless:  I don't know the specific answer to your question, but I suggest you read my posts in this thread:  http://www.agisoft.com/forum/index.php?topic=8948.msg43210#msg43210

I have never tried a project with that many photos at that high of a resolution.  I'm curious to know your results.

Regarding the RAM usage, I have had processing jobs crash with many fewer photos when using the Ultrahigh Dense Cloud setting, even though I have 128 GB of installed RAM.  Increasing the Page File size solved that problem.  But, I have never tried as many photos as you have. 

Good luck!

2

General / Re: Photoscan Error Bad Allocation

« on: July 05, 2018, 08:48:24 PM »

Solution:  I increased the Windows 10 Page File Size (i.e., Virtual Memory) for each computer in the Processing Cluster.  In Win10 this setting can be accessed through:

Control Panel --> System and Security -->  System --> Advanced System Settings (left-hand side) --> Performance (Settings) --> Advanced tab --> Virtual Memory Change... --> Uncheck "Automatically manage paging file size for all drives" and set a custom size.  I set the maximum size to be the same size as my installed RAM.  However, that is likely overkill.  You can play around with the settings based on how much free HDD space you have and monitoring the "Committed" memory usage under the "Performance" tab in Task Manager.

After increasing the maximum Page File Size I know longer had any "bad allocation" errors on projects run on individual machines or processing clusters.

3

General / Re: Photoscan Error Bad Allocation

« on: June 20, 2018, 04:44:57 PM »

Forgot to mention in my previous post:

We are running Photoscan version 1.4.2 build 6205 (64 bit) on all the machines.

4

General / Re: Photoscan Error Bad Allocation

« on: June 20, 2018, 04:43:41 PM »

I'm having a similar problem.  We have set up a network processing cluster with 16 nodes (see configurations below). 

We are trying to process 260 Cameras.  Each photo is 20 MP from a Phantom 4 Pro.  We are processing the Dense Cloud at "Ultrahigh Quality"

During the "Build Dense Cloud" phase on nodes 1 thru 14, we get the following error messages:

2018-06-20 08:04:23 [146.7.96.111:49778] failed #4 BuildDenseCloud.filterDepthMaps (8/13): bad allocation


When I look at the actual nodes we are getting this series of messages in the command console:
BuildDenseCloud.filterDepthMaps (3/13): point colors = 1
loaded camera partition in 0.719 sec
loaded dense cloud data in 1.243 sec
preloading data... done in 254.701 sec
filtering depth maps... Error: Aborted by user
processing failed in 271.804 sec

The node also displays a Windows dialog that says "Your computer is low on memory. Save your files and close these programs: Agisoft Photoscan"


We are having no problems on Nodes 15 and 16.  The memory usage on those machines is running between 50 and 90 GB while processing.

Is there anyway to get around this "Bad Allocation" issue.  Can the Network Server be configured to send smaller batches to the nodes with less RAM so that they do not run out of memory?

Thanks!


Network Processing Node Configurations:

Processing nodes 1 thru 13:
Intel Core i7-7700 3.60 GHz with 16GB RAM
NVIDIA GeForce GTX 1050
Intel HD Graphics 630

Processing node 14:
Intel Core i7-7700 3.60 GHz with 32GB RAM
NVIDIA GeForce GTX 1050
Intel HD Graphics 630

Processing node 15:
Intel Xeon E5-2640 v. 4 @ 2.40 GHz, 10 cores with 256 GB RAM
NVIDIA GeForce GTX 1080 (8 GB RAM)

Processing node 16:
Intel Xeon E5-2643 v4 @ 3.40 GHz, 6 cores with 128 GB RAM
(2X) NVIDIA GeForce GTX 1080 (8 GB RAM)