Reduce IO Load When Starting a Workflow #2075
Merged
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
lkiesow
force-pushed
the
start-workflow-io-load
branch
from
1a08025
to
6a098a1
Compare
|
@lkiesow checkstyle failure, extra import. |
Workflow properties are persisted in the asset manager when a new workflow is started. This requires that a snapshot of the event is already present in the asset manager. Since this is not true for unscheduled events, a snapshot is created on-the-fly. Unfortunately, this can delay ingests if the storage system is under high load and can even cause ingests to fail completely. This patch modifies the behavior by creating a snapshot of an empty media package instead. This significantly reduces the stress put onto storage systems.
lkiesow
force-pushed
the
start-workflow-io-load
branch
from
6a098a1
to
5717de1
Compare
|
Fixed |
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.
Workflow properties are persisted in the asset manager when a new
workflow is started. This requires that a snapshot of the event is
already present in the asset manager. Since this is not true for
unscheduled events, a snapshot is created on-the-fly.
Unfortunately, this can delay ingests if the storage system is under
high load and can even cause ingests to fail completely.
This patch modifies the behavior by creating a snapshot of an empty
media package instead. This significantly reduces the stress put onto
storage systems.
Your pull request should…