Time to run Mesh

[tforward2]

I have a project with 100 photos on this system.
Tie Points: 18 000
Dense Cloud: 55 800 000

Processor: Intel Xeon CPU E5-1620 @ 3.60 GHz
Memory: 16 GB
System Type: 64 bit
GPU: Nividia Quadro 2000

It's 3 and a half hours into building the mesh and says it has another 8 and a half to go. Does this seem normal?

I'm using python to automated the processing and maybe one of the steps is causing it to take a very long time to run.

[Alexey Pasumansky]

Hello tforward2,

If you are running in Arbitrary, the memory consumption can be much higher than 16 GB, so please check that the process has not gone to swap.

[tforward2]

Does texture_size play a role.

I currently have it set to 4096, is there a way to best auto-determine what the texture size should be for build_texture process or does this not effect speed to much.

[waleed121]

When running build mesh it fails and says "Error: bad allocation". What does the mean bad memory allocation? It's using the dense cloud and there are about 261 photos in the chunk.