Native Windows WebODM not utilizing resources

Love that WebODM is now native and not in Docker as I was having unrelated issues with docker.

In any case, I have a dataset of 800+ images that runs fine on the docker setup takes about an hour or so to process and maxes out all threads throughout the process. In the new native version it stays “processing” hours later. It isnt utilizing all processing cores and not using the same amount of memory that the docker version was doing. Ive double checked the settings for max threads and default was set correctly to 24.

Im not quite sure what I’m doing wrong.


Mm, so it processed faster on docker? Was it the same dataset / same settings?

exact same data and settings

Puzzling. Not entirely sure of the cause. We’ll have to investigate.

1 Like

For me, it does not fully use the processor and memory.