You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Find a way to improve the execution time of the ASM Sync process, most likely utilizing SQS
Motivation and context
The current execution time for the ASM Sync process is very long at around 18 days, which is not acceptable - especially if we scale to even more organizations in the future
Implementation notes
Identify possible solutions
Implement and test solution
Bring the ASM sync execution time down to a more reasonable amount
Acceptance criteria
Identify the best way to apply SQS to the ASM sync process to increase performance
Implement the performance improvement
Test the new code
Put the new code into regular use
The text was updated successfully, but these errors were encountered:
arng4108
added
the
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
label
Sep 11, 2024
💡 Summary
Find a way to improve the execution time of the ASM Sync process, most likely utilizing SQS
Motivation and context
The current execution time for the ASM Sync process is very long at around 18 days, which is not acceptable - especially if we scale to even more organizations in the future
Implementation notes
Acceptance criteria
The text was updated successfully, but these errors were encountered: