# Docker WebODM node consuming huge amounts of data

**URL:** <https://community.opendronemap.org/t/docker-webodm-node-consuming-huge-amounts-of-data/19079>\
**Category:** OpenDroneMap Desktop\
**Created:** [January 25, 2024, 7:29pm UTC](https://community.opendronemap.org/t/docker-webodm-node-consuming-huge-amounts-of-data/19079 "2024-01-25T19:29:55Z")\
**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 25, 2024, 8:55pm UTC](https://community.opendronemap.org/t/docker-webodm-node-consuming-huge-amounts-of-data/19079/2 "2024-01-25T20:55:25Z")

</div>

We haven’t had this question in a while, but it’s a valid and interesting one.

> [@HikeAndMap](#):
>
> I just wish to understand what’s going on, because I can’t really understand how out of 10Gb, one would need 80GB processing of temp files for the HDD?

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 processed on machines that don’t have sufficient disk space available. Default: `False`

---

_[View the full topic](https://community.opendronemap.org/t/docker-webodm-node-consuming-huge-amounts-of-data/19079)._