Hello, First of all, congrats on the V1 release of Temporal. :slight_smile: We were using only 1 worker for a couple of running workflows ( 50 000 ) approximately. Workflows instances are mostly waiting for signals to continue. We also have a poller Workflow ( only one instance ) with the NewConti…

Try setting workflow.SetStickyWorkflowCacheSize.

Hello Maxim, SetStickyWorkflowCacheSize seems to be working. [image] Thanks for the help. Pedro Almeida

Hello Maxim, i have same issue in java , where i can set workflow.SetStickyWorkflowCacheSize in java-sdk ? Thanks, Rz

@Rizdian_Dinata for Java set it via WorkflowFactoryOptions#setWorkflowCacheSize, for example: WorkerFactory factory = WorkerFactory.newInstance(client, WorkerFactoryOptions.newBuilder() .setWorkflowCacheSize(myWorkflowCacheSize) .build()); see a…

would like to ask regarding this function as well PurgeStickyWorkflowCache is it recommended to set this during the worker of workflow termination in pod?

Hi @Meli_Lee , for Go SDK: worker.SetStickyWorkflowCacheSize(cacheSize) sets the cache size for sticky workflow cache. This cache is shared between all workers running in the same process and must be called before any workers are started. worker.PurgeStickyWorkflowCache() resets this sticky workfl…

so if we don’t set it during service termination is it fine right ?

If I understand the question correctly: Worker cache is in memory, and calling PurgeStickyWorkflowCache after worker service terminated is not needed cause it would have no effect. Once your workers are back up the server will treat them as completely new workers.

Hi @maxim , I have an problem, when I send 500 request in the same time, It will consume a lot of memory, then I wait for a long time, but memory not decrease, please help me, thank you.

Can you give more info on this? Do you mean memory utilization on your worker processes?

Hi @tihomir [smarter-1w] You can see, ram memory alway increase, not decrease.

Worker Memory usage

Community Support

maxim June 17, 2024, 6:27pm 15

Duplicate of We now have a memory leak problem - #2 by alchemya

Topic		Replies	Views
Identifying Out of Memory causing Temporal Workflows Community Support go-sdk , history , worker	3	1026	January 3, 2025
We now have a memory leak problem Community Support python-sdk	14	2186	March 17, 2026
Reduce memory footprint of temporal process Community Support	4	1086	August 7, 2023
Observing significant memory consumption increase after 1 hour of the workflow completion Community Support java-sdk	3	344	February 20, 2024
RAM memory accumulation Community Support python-sdk	1	71	March 24, 2026

Worker Memory usage

Related topics