Question
Vodafone
ES
Last activity: 2 Aug 2023 9:19 EDT
Materialized IH Summaries - best way to use it in the strategy
Hello!
We manage our Contact Policy in a big strategy that uses a materialized IH Summary. To improve maintainability we want to split the strategy into 4 but, this implies "calling" the IH Summary in each sub-strategy. The question is: Will there be a performance problem if I increase the use of the same materialized IH Summary component? Or, on the contrary, being materialized will allow me to do more than one consult without affecting performance.
Pega recommends having a limit number of IH summary but if I have to limit the times I can use it, the strategies become very difficult to manage.
Thanks
Pegasystems Inc.
US
Vodafone
ES
@Gareth Collins Hi! thanks for you response.
The main strategy does not call to IHSummary in the new desing. The callings are produced in each sub estrategy with they corresponding filters before to call IHSummary shape, so the IH summary will be called 4 times instead 1 (the same IHSummary). There will be performance cost?
What I need to confirm is:
When there is a consult to IHSummary, the information is hold in memory or something like that? or the information is load every time I call IHSummary ?
In the second scenary I assume there will be performance cost.
Thank you very much
@AbigailC4214If these sub-strategies are all executed from one main strategy (i.e. there is one strategy shape in the dataflow), then there should not be a performance cost assuming that any filtering of summary pages is done in the strategy after the IH summary shape (i.e. the IH summary shape is not used in "driven mode" with a list of propositions fed into it). The strategy will lookup Cassandra once and provide the same results and provide the same results to each additional call to the IH summary shape.
Does that answer your question?