Allow to run occ preview:repair in parallel#22911
Merged
Conversation
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Contributor
|
I would suggest for the lock messages. More information: https://symfony.com/doc/current/console/verbosity.html |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
Member
Author
Done. |
skjnldsv
approved these changes
Sep 17, 2020
Member
|
@MorrisJobke backport? |
Member
Author
To 20 yes. |
Member
Author
|
/backport to stable20 |
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
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.
Wit this
occ preview:repaircan be run multiple times in the same instance and will share load between those. It will still process the directory as a whole, but skip locked folders. In this way the processes can run on multiple machines to avoid some bottlenecks like network IO.The output for one process out of 3 parallel tasks then might look like this:
One can see that two folders are locked and skipped and the third one is processed.
Regarding the timing it seems to be harder to judge, but the overall load is less and the total user time is 9.7s (single process) vs 12.2s (3 processes) and the total system time is 2.3s vs 3.5s (3 processes). It completed after 21s (single process) cs 10 seconds (3 processes). The overhead due to the additional skips can be seen, but it can be distributed across multiple machines or even more processes.
Raw timings: