Use the job wall clock timeout for time limit estimation #987
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
|
Not sure of the behavior of this metric in virtualized environments. It could be worth to perform some comparisons. |
|
|
|
There is no optimal solution to this issue right now. The wall time is better for multithreaded projects because it is always larger than the running time. However, for most monothreaded projects (and the most common exercise type), the value is far away from the reality. I think you should keep track of this issue in #989 for later in order to provide a better time estimation. |
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.
By default the CPU time is used, which is not a real time metric. Using it to provide user feedback on job completion is not appropriate in multi-core environments.