RJKSolutions

(AFSDK 2.6) Length of PE Analysis Rule ConfigString

Discussion created by RJKSolutions on Nov 27, 2013
Latest reply on Nov 28, 2013 by Gregor

Is there a limit to the length of the ConfigString for the PE Analysis Rule?

 

I'm trying to judge how best to scale out 1,000's of calculations that are not specific to an asset hierarchy - i.e. a flat structure. I see that the expressions for a rule are part of the AR ConfigString ("{Variable} := {Expression};"), variable mappings are minimal & no concern ("{Variable}||{Output};") and with the expressions being quite lengthy initially (there will be subsequent iterations to break down calculations), does it make sense to either break down the calculations with the same time rule into multiple AR instances, or it is perfectly fine to bunch 1,000's of calculations into a single AR instance? I'm assuming the initial parsing of the config string by the analysis scheduler is the overhead, once the calculation is running its running...

 

I've done this automatically via code so need to know now which approach is recommended to alter my logic accordingly.

Outcomes