Optimize JournalRepository #2007
Merged
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.
findWhere
retrieves all entries matching thewhere
statement, meaning we were fetching all those entries and then summing them manually, which was not optimized. With this PR, we now sum directly in SQL.This results in a huge improvement for large journals -
FinanceEventHandler
execution time dropped from over 13 seconds to less than 1 second on my prodChanges in
app/Repositories/JournalRepository.php
:findWhere
towhere
inrecalculateBalance
function to improve query consistency.Should be applied to both
v7
andv8