Camunda 7 script performance: JUEL vs groovy

Hi folks,

I’m trying to do some performance optimization for the execution flow in the high-loaded BPM service.
Apart from everything else I found calls of groovy inline scripts in the flow conditions like:

execution.getVariable("isOK") == true

Are there any performance benefits to use JUEL in condition expressions over groovy?

For a simple variable evaluation like that, why call out to a script at all?

If the condition is ${isOK} that would evaluate to a boolean.
This should result in slightly improved performance, as you’re not calling out to the script engine on each evaluation.

In C7, you can do things like ${x==1} for your evaluations, and it will be evaluated in the engine instead of calling the scripting engine. Reference Data-based Exclusive Gateway (XOR) | docs.camunda.org

This is not my solution, I’m just auditing the process structure and code. And I have the same concerns that calling the scripting engine instead of evaluating expressions can hurt performance.

But I need facts for developers. I think I will do some load testing and collect metrics.

Thanks.