Production deployments of OpenDroneMap do require tuning. Defaults often work fine, but your workflow, user base, datasets will drive the tuning of the deployment.
In short, see the third answer in the search here:
https://community.opendronemap.org/search?q=space%20order%3Alatest
Direct link as follows:
You can also set up your NodeODM deployment to clean up more often, which allows you to centrally control the cleanup schedule and doesn’t require your users to remember to use the correct flag. It has slightly different implications to optimize-disk-space insofar as task sub-products are retained for a period rather than cleaned up along the way, but be careful setting it to too small a value.
--cleanup_tasks_after <number> Number of minutes that elapse before deleting finished and canceled tasks (default: 2880)
--cleanup_uploads_after <number> Number of minutes that elapse before deleting unfinished uploads. Set this value to the maximum time you expect a dataset to be uploaded. (default: 2880)
See also in the link above info on expected space usage for processing intermediates.
Also, I cannot wait to redo the docs, but what’s there is good and also quite searchable when the results on the forum are insufficiently structured:
