Memory footprint of ExecutorThreads

Hey there,

I was recently analyzing a HeapDump from one of our Camunda SpringBoot apps and I stumbled upon several TaskExecutor-threads, which held a large number of TimerEntites in the Entity-Cache of Camunda’s CommandContext - including their JSON payload. Some of the threads held over 70k TimerEntities and occupied more than 250MB heap.

Can anyone explain what this is needed for? Is there a way to configure the entity cache size? Is it recommended to have such a big cache?