[Catalog Promotion] Move catalog promotion processing after the fixture execution #13579
Conversation
This file contains 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
GSadee
approved these changes
Feb 2, 2022
|
This looks dangerous for me cause cleaning whole entity manager means that you remove everything that was put in it, either it was already saved or not into database, which means side effects in live applications can be unpredictable IMHO. |
|
I agree with @stloyd. Usually it's flush then clear, doing just a clear is not a good idea. |
lchrusciel
force-pushed
the
cp-clear-wrapper
branch
from
017d886
to
f3af065
Compare
lchrusciel
changed the title
GSadee
approved these changes
Feb 3, 2022
lchrusciel
force-pushed
the
cp-clear-wrapper
branch
from
f3af065
to
b4b5220
Compare
lchrusciel
force-pushed
the
cp-clear-wrapper
branch
from
b4b5220
to
ee3a2da
Compare
|
Thanks, Łukasz! 🎉 |
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.
Previous:
With clearing entity manger we don't need to trace that many objects in UnitOfWork, therefore we are not calculating that much changes and we save ton of memory.Ref. https://blackfire.io/profiles/compare/7c9cb9fd-c43f-4420-8e0a-0af2a7b4b000/graphNow:
Just a refactor of CP fixtures. The EntityManager will be cleared with https://github.com/symfony/doctrine-bridge/blob/5.4/Messenger/DoctrineClearEntityManagerWorkerSubscriber.php just by the fact, that it will be processed asynced. Which will be done in #13578.
#13578 vs previous implementation -https://blackfire.io/profiles/compare/f560f723-f970-41b3-ac1a-7fe3a8858d77/graph