# Huge number of executions

**URL:** <https://forum.camunda.io/t/huge-number-of-executions/25151>\
**Category:** Discussion & Questions\
**Tags:** process-engine\
**Created:** [January 27, 2021, 9:15am UTC](https://forum.camunda.io/t/huge-number-of-executions/25151 "2021-01-27T09:15:59Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![andrius](https://forum.camunda.io/letter_avatar_proxy/v4/letter/a/73ab20/32.png) [@andrius](https://forum.camunda.io/u/andrius)\
**Post date:** [April 2, 2021, 3:49pm UTC](https://forum.camunda.io/t/huge-number-of-executions/25151/15 "2021-04-02T15:49:46Z")

</div>

Ok, I was able to solve the first issue using some listener magic suggested here: [Set local variables in event subprocess via REST-API - #9 by Marc1](https://forum.camunda.io/t/set-local-variables-in-event-subprocess-via-rest-api/13157/9)  
It seems unnatural not being able to send local vars to event subprocess in a civilized manner. Others are also complaining about it:  
[https://jira.camunda.com/browse/CAM-10380](https://jira.camunda.com/browse/CAM-10380)  
[https://jira.camunda.com/browse/CAM-10680](https://jira.camunda.com/browse/CAM-10680)

I’m still not able to deal with the evil OptimisticLockingException problem. Why oh why Camunda needs any locking on event subprocesses started by uninterruptible message event? Resolving those locking problems kills the performance when dealing with many small items.  
How do I work around it?

---

_[View the full topic](https://forum.camunda.io/t/huge-number-of-executions/25151)._
