# Memory management strategy of temporalite

**URL:** <https://community.temporal.io/t/memory-management-strategy-of-temporalite/5886>\
**Category:** Community Support\
**Tags:** temporalite\
**Created:** [September 5, 2022, 6:21am UTC](https://community.temporal.io/t/memory-management-strategy-of-temporalite/5886 "2022-09-05T06:21:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![whitecrow](https://avatars.discourse-cdn.com/v4/letter/w/50afbb/32.png) [@whitecrow](https://community.temporal.io/u/whitecrow)\
**Post date:** [September 5, 2022, 6:21am UTC](https://community.temporal.io/t/memory-management-strategy-of-temporalite/5886/1 "2022-09-05T06:21:20Z")

</div>

What is the memory management strategy of temporalite in-memory mode?  
Is there an upper limit of the memory consumption?  
I observed that the memory consumption continuously growing as number of workflow executions grow:

 ![截屏2022-09-05 下午2.16.19](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/3/311de9d5263d1de63f21246fd7d0690b6473983b.png)

If there is an upper bound, then:

1. How can we configure it?
2. What happens when it is hit?

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [September 5, 2022, 12:56pm UTC](https://community.temporal.io/t/memory-management-strategy-of-temporalite/5886/2 "2022-09-05T12:56:44Z")

</div>

Temporalite is similar to [auto-setup](https://github.com/temporalio/docker-builds/blob/main/auto-setup.Dockerfile#L26) as in it starts all service roles in the a single process. This makes it imo hard to find out which service would need to be looked at (especially without server metrics).  
My best guess would be to try to look at dynamic config settings for history service cache, see more info [here](https://community.temporal.io/t/history-service-memory-usage/5569/4).