Increase performance limits for T0 workflows #3978
Merged
Conversation
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
T0 run in a special setup where memory limits can be higher and runtime is 1 week
hufnagel
added a commit
that referenced
this pull request
Sep 27, 2012
Increase performance limits for T0 workflows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
T0 run sin a special setup where memory limits can be higher and runtime is 1 week.
@hufnagel, can you commit this before making the release please. This avoids having job failing because memory limits (specifically VSize limit which has a low default). I ran the RunConfig_t and Tier0Feeder_t test and it checks out
I don't know if we ever wanna have those configurable though.