In Camunda 7(v7.14.5-ee), Deployment Cache not getting Enabled.

Hello, We are working on high TPS(orders per second) requirement in Camunda (250 TPS). We observe there is high volume of SQL queries(SELECT) in DB tables (act_re_procdef,act_re_decision_def). After the SELETE the connection stays in ‘Idle in Transaction’ for long period, we are using postgres 13.1 DB.
Eg Query :
select * from ACT_RE_PROCDEF RES where KEY_ = ? and TENANT_ID_ is null and VERSION_ = ( select max(VERSION_) from ACT_RE_PROCDEF where KEY_ = ? and TENANT_ID_ is null)

We are trying to find a solution where these definitions can be directly read from Camunda Cache. We tried below options but the repeated SQL queries are still visible in profile.
Please help if there is a way to omit these repetitive queries.
———————————Options tried———————-
camunda:
bpm:
process-engine-name: default
enable-duplicate-filtering: true
deployment-resource-pattern: classpath:/processes/*.bpmn
process-definition-cache-limit: 1000

camunda:
bpm:
process-engine:
cache-capacity: 1000

camunda:
bpm:
deployment-cache:
capacity: 1000
——————————————————

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.