Closed axelstudios closed 4 months ago
Importing data into a large organization can take a considerable amount of time to go through the matching/merging/linking process
Optimizes several steps throughout the import process to improve performance:
Matching Data (3/6): Merging Unmatched States
When importing 512 records that will merge into an org with 512 records, with UBID data:
When importing 5000 records that will merge into an org with 145,000 records, without UBID data:
When importing 40,000 records that will merge into an org with 145,000 records, without UBID data:
Matching Data (4/6): Merging State Pairs
Upload files into existing organizations using develop and this branch - compare the runtime
Any background context you want to provide?
Importing data into a large organization can take a considerable amount of time to go through the matching/merging/linking process
What's this PR do?
Optimizes several steps throughout the import process to improve performance:
Step
Matching Data (3/6): Merging Unmatched States
When importing 512 records that will merge into an org with 512 records, with UBID data:
When importing 5000 records that will merge into an org with 145,000 records, without UBID data:
When importing 40,000 records that will merge into an org with 145,000 records, without UBID data:
π₯π₯π₯π₯π₯
π₯π₯π₯π₯π₯
Step
Matching Data (4/6): Merging State Pairs
When importing 512 records that will merge into an org with 512 records, with UBID data:
When importing 5000 records that will merge into an org with 145,000 records, without UBID data:
Total timing when importing 512 records that will merge into an org with 512 records, with UBID data:
How should this be manually tested?
Upload files into existing organizations using develop and this branch - compare the runtime
What are the relevant tickets?
4549