Thanks for the feedback. I would comment on the parts of your answer.
We are not using database as log data storage, so we did examine wis files even prior to this question. There we have, as you described, duration of the workflow execution, in total, as well as for separate steps - scoring plans.
I.e we have scoring_XXX as plan executed and in wis file written:
<workflowTaskPersistModelBean stopped="2020-04-27 14:41:37" started="2020-04-27 10:51:57" id="scoring_XXX" state="FINISHED_OK">
And that’s it - here no more useful info, in regards to my question.
wfinst_ folder, and scoring plan XXX subfolder does have task.log file, but again there are no useful info in regards to my question. In task.log you can find list of parsed steps from the plan and they have just one date/time info for all, in this case, I.e. 2020-04-27 10:51:58, INFO and DEBUG statements for processed steps, and at the end 2020-04-27 14:41:37 INFO: Finished! (Time spent: 13778 s)
I can analyse the execution within IDE while executing, via Console and details there, but this is not so adequate, since there is no proper written trail, and no way for comparison of multiple data read and rules execution. Real time info gathering is rather not an option for us. If there is a way to write these data during the execution in log file, that would be OK, we can (batch) parse those files later on, for comparison.
That’s why we are trying to narrow down the number of reasons for execution slowdowns, initially with this question, to see if the issue if with the data source read,
or complexity of the rules.
I would appreciate any further comments or ideas from your side, but I thank you anyway for the effort and support thus far.