# Optimizing Dask worker memory for writing Zarr files from GeoTIFs

**URL:** <https://discourse.pangeo.io/t/optimizing-dask-worker-memory-for-writing-zarr-files-from-geotifs/4475>\
**Category:** Data\
**Created:** [September 3, 2024, 1:47pm UTC](https://discourse.pangeo.io/t/optimizing-dask-worker-memory-for-writing-zarr-files-from-geotifs/4475 "2024-09-03T13:47:19Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![TomNicholas](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/tomnicholas/32/3189_2.png) [@TomNicholas](https://discourse.pangeo.io/u/TomNicholas)\
**Post date:** [September 5, 2024, 4:28pm UTC](https://discourse.pangeo.io/t/optimizing-dask-worker-memory-for-writing-zarr-files-from-geotifs/4475/3 "2024-09-05T16:28:30Z")

</div>

FYI these kind of frustrations with dask are what motivated development of [Cubed](https://discourse.pangeo.io/t/pangeo-showcase-cubed-bounded-memory-serverless-array-processing-in-xarray/3836), which aims to be transparent and predictable about per-worker runtime memory usage.

---

_[View the full topic](https://discourse.pangeo.io/t/optimizing-dask-worker-memory-for-writing-zarr-files-from-geotifs/4475)._