Optimize Docker usage by enabling container reuse #2444
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.
Why are these changes needed?
These changes aim to enhance the efficiency of the DockerCommandLineCodeExecutor by allowing it to reuse existing Docker containers instead of starting a new one for each code execution.
This approach not only speeds up the code execution process by reducing the overhead associated with container setup and teardown but also aligns with sustainable resource usage practices.
Although these changes do not fully resolve #741, they incorporate the suggestion from bbence84 on the potential performance improvements from reusing containers.
Related issue number
Partially addresses #741 and somewhat related to #929
Checks