Optimzation and Performance Issues

[philip-alldredge]

• Hot spots based on previous profiling:
  • DefaultReferenceService.getRelativeReference
    • Caused by DI? Could be solved by converting reference builder into a fixed interface. Inject services into constructor. This could also be caused by the code building relative references for the same object repeatedly. Profile again to determine root cause. Query system/Business Object Context could be optimized to only create the appropriate reference once. Could have a special interface if necessary for the optimized case.
    • Other Notes:
      • buildSimpleRelativeReference is a small but signfiicant %.
      • RelativeBusinessObjectRference init is a signficant chunk of that too
  • GraphitiAgeDiagram.updateDiagramElement()

[philip-alldredge]

The root cause seems to be building relative reference for the same objects repeatedly while executing queries. Rather than optimize the reference builder API, the query service was extended to allow diagram elements to provide its business object's relative reference. This allows queries to run without needing to build as many relative references.

[philip-alldredge]

This optimization effects users of:
Query.descendantsByBusinessObjectsRelativeReference
Query.filterByBusinessObjectRelativeReference

This change will need significant testing before merging. The primary users of those methods are the business object handlers for business objects which are represented as connections.