I am using camunda 8…and have a process defined in it…same process is also in legacy and we are not using camunda 24*7…it is up for certain time only…the problem is when camunda start and legacy stops all the pending cases are transfered to camunda at once…since i have lot of job worker it slows down and processing takes lot of time…
is there a way i can handle this and maybe put some instances in wait state after it starts and process then in batch or maybe process them few at a time…I cannot start the instances in batch because it is automatically triggered after legacy stops working
I’m still not clear on exactly where your bottle neck is - you have 6k processes per?? second? I’m not sure if the issue is that the processes aren’t starting or that there’s a large number waiting or that they’re not passing through the process quickly enough. Can you clarify.
Absoltuly, It’s likely to get through more instances if there are more workers working on each job type. So spinning up more workers is likely to help with individual processing.
I’d also suggest adding more brokers, maybe 5 or 7 that’ll be able to move the processes through faster as well.
@Sarthak_Saumya
Please do not delete your posts from the thread once the thread is solved. It makes it very difficult for others to come in and understand what’s going on.
The data is still there. IF you have confidential data, don’t post it, but that may impact your ability to get help from the community. This is a community forum, not an official support channel. Camunda will be happy to offer you a support contract if you have specific support needs.