Resolving concurrency conflcts during fetching operation #1243
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.
Thank you for taking your time to contribute to Ersilia, just a few checks before we proceed
Description
A session ID mechanism to manage resource allocation during fetching, ensuring the successful execution of models running simultaneously across different sessions.
Changes to be made
Updated the tmp directory prefix to include Session PID.
Status
Simultaneous fetching of models from different sources now works seamlessly. Ersilia no longer attempts to shut down Docker containers for models pulled from Docker Hub running in other sessions.
To do
Resolve concurrency conflicts in serving and running predictions.
Related to #1197