Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
trunk
-
None
Description
Background
When creating entities with Atlas at scale, few inefficiencies were observed.
They were:
- GraphHelper.getAdjacentEdgesByLabel: The existing approach results in high memory usage. The method could use graph api that already exists.
- AtlasRelationshipStoreV2.getRelationshipEdge: This does full vertex comparison. This is expensive.
- Edge label is not index. Indexing this will improve speed of edge by label lookup.
Solution
Profile Atlas with (using metrics) to establish baseline.
Use the fixes mentioned to the places above and profile.
Attachments
Attachments
Issue Links
- contains
-
ATLAS-669 GraphHelper.getEdgeForLabel() can use edge index
- Resolved