Question
Morgan Stanley
IN
Last activity: 2 Aug 2018 9:17 EDT
How does saving as a property in subclass impact performance
I usually find the below error message when we try to save as a property in parent class in subclass for various reasons:
|
A property of this name already exists within the inheritance path. Consider removing duplicate property definitions as they can negatively impact system performance.
|
ex: pxAssignedOperatorID
How does property saving impact performance.
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
CollabPartnerz
IN
Above message tells that you are un necessarily creating same property.
If already property exist in inheritance path,creating a same property is useless.
Pegasystems Inc.
FR
Yes absolutely, you should always avoid unnecessary rules creation. Mainly for better (easiest) maintenance of your application and in the end for best application performance.
Morgan Stanley
IN
Thanks for the replies.
I understand that we should avoid duplicating properties.
But for example a property pxAssignedOperatorID, is saved in 5 classes with a slight change of reference (linked property).
In such cases what impact does it have on the performance.
I'm specifically trying to understand the performance impact.
Pegasystems Inc.
FR
hello,
I believe (but it might not be the full explanation) this is just adding more rules to be checked by our rule resolution mechanism. So the more rules you having longer it will takes but I don't think we have any metrics about this.