memory consumption of BuildOrthomosaic.buildPartition stage

[MichalDV]

Hi guys,

do you have any tip on how to reduce memory impact of buildPartiton stage of Ortho generation? my project is chewing up more than 350GB of virtual memory 

[Alexey Pasumansky]

Hello MichalDV,

What parameters were used for the Build Orthomosaic stage and which version of Metashape you are using?

[MichalDV]

Hi Alexey,

settings are:
projection = WGS 84, surface = DEM, blending mode = Mosaic, refine seamlines = 0, ghosting filter = 1, pixel size = 1.56575e-07 x 1.00651e-07

version is 1.7.5 b 13229 64bit on windows.

[Alexey Pasumansky]

Hello MichalDV,

Than you for providing the processing task parameters. Can you please confirm, if the RAM consumption is normal, if you disable ghosting filter option?

Additionally please specify the expected size of the orthomosaic in pixels, number of images in the project and image dimensions in pixels, DEM resolution in m/pix and number of CPU cores of the computer used for the processing.

[MichalDV]

There is 9160 images with resolution of 8192x5460, flown with DJI P1 camera, DEM has 4 447 Mpix, we have 32 cpu cores (Ryzen 5950x) Estimated ortho dimensions are 144523x123063

Our goal is to hit resolution something around 1cm/px
I will try disabling ghosting filter and get back to you.

[MichalDV]

Without ghosting filter it seem to fly through buildPartition stage with almost none ram consumed.

[Alexey Pasumansky]

Hello MichalDV,

OK, thank you for additional information, we'll analyze the reported behavior on similar projects.

[Corensia]

Hi Alexey,

We had the same issue with just 367 images taken with the DJI P1 camera and using a 128 GB RAM PC when we saw this post. Disabling ghosting filter also solved our 'not enough memory' issue.
Is this something that will be addressed in a future update or is ghosting filter not an option with DJI P1 camera images greater than 350+ or so images?

David