Hi Team, i am using Camunda 7.11 with mysql. We are using only rest api services integrated in our application.
Sometimes i could see slowness in submit start api (Document link). If I keep on resend the same request i don’t see any slowness. I could not figure out the reason behind this.
I struck with this issue since 2 weeks . Please help me to understand why this behaviour and also kindly provide your valuable inputs to resolve my issue.
Thanks in advance.
hello friend!
take a look where your Camunda was deployed to see if it is not overloaded.
You can also verify that connection pooling is not overloading start.
But since you said that the first call is slow, and the next ones take a while, it’s looking like something related to the cache… it would be interesting to see this.
Regards.
William Robert Alves
Also consider using a newer version of Camunda, preferably one later than the version you are using that has some bug fixes and performance improvements that might help!
Hi @aniinprni,
could it be that you have an asynchronous continuation in your process model and the Backoff strategy of the Job acquisition takes a while to acquire the first job in the morning: The Job Executor | docs.camunda.org?
Hope this helps, Ingo
Hi @Ingo_Richtsmeier , there is no asynchronous continuation in our model . its a simple bpmn model contains only 2 user tasks . Last 6 months we don’t see any issue like this, but from last month onwards the issue has been occurring. For a simple user task with yes or no conditional gateway, is Job executor going to play a major role ? FYI, We are running 6 camunda pods in the production.
Hi @WilliamR.Alves , Thank you for your reply. How i can check this cache thing? how do we disable this cache ?
Hello my dear @aniinprni ! \O
When I talked about caching, I meant to check if the delay in the first API call, and the speed in the other calls, can’t have anything to do with caching… Because maybe your application has a proxy or something like that, which intercepts the API call and “save” the important data for the other calls.
So in the first API call as the proxy has not yet saved the information in cache, it ends up taking a long time, and in the next calls the proxy already has the relevant information to do and ends up making the API call quickly… something like this .
I suggest checking with your architecture team, and commenting on this case, maybe they can give you a suggestion or even adjust something in the project.
Regards.
William Robert Alves
In your process do you have only user tasks?
Don’t have service tasks?
Do these user tasks only communicate with the Camunda API or do they communicate with some other API?
Have you tried making the API call manually through Postman or Insomnia and checking the time it takes to get the response?
Hi @WilliamR.Alves , I have verified via postman number of times. I could not see slowness in the API level. with your input i will try to connect with my devops team today and get back to you.
Thank you so much for your valuable information.