Optimize entity deletions in multiple methods by batching operations into single transactions #7702
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ategories, and ProductManufacturers to use batch deletions in a single transaction instead of individual db calls
makhsudov-mz
approved these changes
May 13, 2025
|
Hi @atiq-bs23! Thank you for your help |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, entity deletions were executed one by one using individual async calls, which introduced unnecessary database round-trips. This PR optimizes the following methods to delete lists of entities in bulk within a single transaction:
DeleteProductAttributeValuePicturesAsyncDeleteProductCategoriesAsyncDeleteProductManufacturersAsyncThis improves performance.