# Using Dask client and running out of memory

**URL:** <https://discourse.pangeo.io/t/using-dask-client-and-running-out-of-memory/3500>\
**Category:** Science\
**Created:** [June 8, 2023, 5:17pm UTC](https://discourse.pangeo.io/t/using-dask-client-and-running-out-of-memory/3500 "2023-06-08T17:17:52Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![chase](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/chase/32/2596_2.png) [@chase](https://discourse.pangeo.io/u/chase)\
**Post date:** [June 9, 2023, 12:33am UTC](https://discourse.pangeo.io/t/using-dask-client-and-running-out-of-memory/3500/3 "2023-06-09T00:33:26Z")

</div>

I had a similar issue with a different problem [see here](https://discourse.pangeo.io/t/am-i-thinking-about-this-data-processing-chunking-workflow-correctly/3345/8). By monitoring the dask dashboard I could see that workers were consuming more memory than I stated for the memory limit.

As a test you could try reducing the memory limit and monitor the dashboard to see how much memory is actually being consumed, as Guy suggested.

---

_[View the full topic](https://discourse.pangeo.io/t/using-dask-client-and-running-out-of-memory/3500)._