Improve fixture loading while increasing the number of fixtures #522
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #522 +/- ##
============================================
+ Coverage 36.35% 37.61% +1.25%
+ Complexity 1152 1121 -31
============================================
Files 186 181 -5
Lines 4627 4472 -155
============================================
Hits 1682 1682
+ Misses 2945 2790 -155 ☔ View full report in Codecov by Sentry. |
0x46616c6b
force-pushed
the
Improve-fixture-loading-while-increasing-the-number-of-fixtures
branch
from
e06a8eb to
1f4d449
Compare
0x46616c6b
deleted the
Improve-fixture-loading-while-increasing-the-number-of-fixtures
branch
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.
I attempted to increase the fixtures to replicate the issues with "large" datasets. However, I encountered a problem where there was insufficient memory, and it took a long time. Consequently, I decided to refresh my Doctrine skills and optimize the database operations. Additionally, I optimized the password hashing for fixtures since we utilize the same password for all fixtures, eliminating the need to recalculate it for each user.