IterationDepthScan Performance


[CDR: ehrbase]

We have a few templates which requires IterationDepthScan AQL config in ehrbase properties to be increased to 20, but with this change we see there is performance impact, there is atleast average of 500-1000 ms difference while running AQL’s, When looked through the code, could not see much scope on optimizations since this property is more or less used when constructing SQL, is this a known issue, did anyone face similar sort of issue, or is there a better way to handle this use-case without having much impact on AQL performance.

Thanks in advance

This setting will be removed in further version of ehrbase and then there will be performance improvements but I can not give you a time frame.

1 Like

Thank you for update @stefanspiska

1 Like