# Out of Memory - frozen system - ubuntu/docker

**URL:** <https://community.opendronemap.org/t/out-of-memory-frozen-system-ubuntu-docker/19125>\
**Category:** OpenDroneMap Desktop\
**Created:** [January 29, 2024, 2:32pm UTC](https://community.opendronemap.org/t/out-of-memory-frozen-system-ubuntu-docker/19125 "2024-01-29T14:32:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![smathermather](https://community.opendronemap.org/user_avatar/community.opendronemap.org/smathermather/32/876_2.png) [@smathermather](https://community.opendronemap.org/u/smathermather)\
**Post date:** [January 29, 2024, 3:01pm UTC](https://community.opendronemap.org/t/out-of-memory-frozen-system-ubuntu-docker/19125/2 "2024-01-29T15:01:16Z")

</div>

> [@jstroup](#):
>
> I have not researched this situation - so I don’t know if this situation has been documented and commented upon in the past.

> [@jstroup](#):
>
> But it seems clear to me that until it is addressed, it would be problematic to use the Docker implementation of WebODM in any sort of production facillity.

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](https://community.opendronemap.org/search?q=space%20order%3Alatest)

Direct link as follows:

> [@Docker WebODM node consuming huge amounts of data](https://community.opendronemap.org/t/docker-webodm-node-consuming-huge-amounts-of-data/19079/2):
>
> We haven’t had this question in a while, but it’s a valid and interesting one. For safe measure, I usually tell folks to have 10x the storage of their input data, so 8x makes sense as an actual value you’re seeing. You’ve got a couple options, but the simplest is to add the optimize-disk-space flag: [optimize-disk-space](https://docs.opendronemap.org/arguments/optimize-disk-space/#optimize-disk-space) Delete heavy intermediate files to optimize disk space usage. This affects the ability to restart the pipeline from an intermediate stage, but allows datasets to be processe…

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.

```auto
--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:  
[![image](https://community.opendronemap.org/uploads/default/original/2X/2/246cce54f0fda5bfc3d10789eec987cb828129cd.png)](https://docs.opendronemap.org/search/?q=space&check_keywords=yes&area=default)

---

_[View the full topic](https://community.opendronemap.org/t/out-of-memory-frozen-system-ubuntu-docker/19125)._