The contents of this page is are meant as a general guide to list considerations that might impact the performance of your Duplicate UDR SQL storage setup. Note that each setup may vary and that these are not strict rules that users should apply for all their Duplicate UDR SQL storage setupsetups.
File vs SQL Storage
Generally, there would be some performance overhead when choosing to use SQL storage instead of File storage, but there are benefits that an SQL storage could provide depending on your needs that makes make the performance overhead acceptable. The purpose of this guide is to offer several recommendations that you may apply to minimize the performance overhead of your SQL storage setup.
...
Performance may be better when the "Enable Separate Storage Per Workflow" option is disabled.
...
From our performance tests for SAP Hana SQL storage specifically, the use of columnar column-based table tables compared to row-based tables showed strong advantages in performance and disk space footprint.
There were unexpected issues during our tests when the memory capacity of the machine where SAP Hana was installed was too small. We experienced minimal issues when installing SAP Hana database with a 64GB memory capacity.
...
The Indexing Field of incoming UDRs should preferably be either an increasing sequence number or a timestamp with good locality to preserve the performance of workflow executions.
For large cache sizes, it may be a good idea to split them to into multiple workflows in order to preserve performance.
For large cache sizes, splitting batches of incoming UDRs into multiple transactions may improve the performance of workflow runs.
Minimizing the cache size may improve the performance of the duplicate checks by the Duplicate UDR agents and the speed of Search and Delete operations using the Duplicate UDR Inspector.
...