Meshroom not use gpu?

[trburns2007]

I have yet to see meshroom use any of my GPU. Only 100% of my CPU. Is this normal?

[skinkie]

Currently only some parts of the pipeline can use an Nvidia GPU via CUDA. For example the second step "feature extraction" when SIFT is selected. In the logs you would read that it is using the GPU. If AKAZE is selected it would be computed over the CPU.

[natowi]

In FeatureExtraction disable "Force CPU Extraction" to use the GPU for this node. The GPU code is (at the moment) not optimized to utilize all available ressources.

[ErikUden]

How do I turn --forceCpuExtraction to false when using Meshroom's GUI? It's not something I can change as an attribute in the FeatureExtraction node.

[skinkie]

@NotErikUden

[ErikUden]

Thank you so much! All is resolved. (Petition to remove "advanced attributes" button. We're using Meshroom, we're not amateurs! :D)

[natowi]

Thank you so much! All is resolved. (Petition to remove "advanced attributes" button. We're using Meshroom, we're not amateurs! :D)

@NotErikUden Most Meshroom users are in fact amateurs and hiding the advanced options reduces questions regarding settings that require in-depth knowledge of the used algorithms (and no real benefits for the user in most of the cases). The advanced options are intended for developers to test the results for specific parameters. Some features like GPU extraction are not stable and can cause issues ("out of memory" for example), therefore they are hidden for the casual user until they are production ready.

[rutvikokate]

How do I turn --forceCpuExtraction to false when using Meshroom's GUI? It's not something I can change as an attribute in the FeatureExtraction node.

How to turn this off in command line?

[ChemicalXandco]

@rutvikokate are you using meshroom_compute or meshroom_batch?

[rutvikokate]

@rutvikokate are you using meshroom_compute or meshroom_batch?

meshroom_batch

[ChemicalXandco]

@rutvikokate you can add the argument --paramOverrides FeatureExtraction:forceCpuExtraction=0

[rutvikokate]

@rutvikokate you can add the argument --paramOverrides FeatureExtraction:forceCpuExtraction=0

Okay thanks!

[WellTung666]

@rutvikokate are you using meshroom_compute or meshroom_batch?

How to it off when using meshroom_compute ? thanks!

[ChemicalXandco]

@WellTung666 you must change the setting in the meshroom file (.mg). You can do it in a text editor but I recommend doing it in the meshroom GUI if possible.

[WellTung666]

@WellTung666 you must change the setting in the meshroom file (.mg). You can do it in a text editor but I recommend doing it in the meshroom GUI if possible.
Thanks！But i need to run on server.Or do you koew how to turn it off using meshroom_photogrammetry(Meshroom-2019.1.0).

[ChemicalXandco]

Meshroom-2019.1.0

Is there any reason why you can't use 2021.1.0? That is the latest version which has many improvements.

do you know how to turn it off using meshroom_photogrammetry

Please look at my comment above but it only works in versions 2020.1.0 and up.

[WellTung666]

Meshroom-2019.1.0

Is there any reason why you can't use 2021.1.0? That is the latest version which has many improvements.

do you know how to turn it off using meshroom_photogrammetry

Please look at my comment above but it only works in versions 2020.1.0 and up.

OK Thanks!

[busyBeaver1]

Hello. Im having a similar problem. @skinkie 's screenshots helped a lot with the FeatureExtraction step. But what about other steps? It still uses a lot of cpu, for example, on FeatureMatching. Maybe there are other options to use gpu on other steps?

[natowi]

GPU support can optionally be enabled for featurextraction and is required for depthmap. Other nodes do not have gpu support.