Update storage section to explain relocatable python venvs with uv #47
Conversation
|
preview available: https://docs.tds.cscs.ch/47 |
egparedes
force-pushed
the
relocatable-venvs-with-uv
branch
from
096ce8a to
eb89002
Compare
|
preview available: https://docs.tds.cscs.ch/47 |
1 similar comment
|
preview available: https://docs.tds.cscs.ch/47 |
|
I'm sorry for requesting a review before it was ready (I forgot to commit some changes). Now it should be ready. |
No worries! Review requests have been added automatically because we added ourselves to the |
|
preview available: https://docs.tds.cscs.ch/47 |
docs/guides/storage.md
Outdated
|
|
||
| In our "simple" pytorch example, I counted **22806 inodes**! | ||
|
|
||
| ##### Alternative virtual environment creation using uv |
There was a problem hiding this comment.
Instead of adding the uv method as a sub-heading under the pip method, how about putting them at the same level as tabs?
With one tab for pip, and one for uv (I would be fine with making the "first" default tab the uv one, so that we can push users towards uv.
https://squidfunk.github.io/mkdocs-material/reference/content-tabs/#usage
There was a problem hiding this comment.
See here for an example of what tabs look like in our docs
https://eth-cscs.github.io/cscs-docs/software/tools/linaro/#quickstart-guide
egparedes
force-pushed
the
relocatable-venvs-with-uv
branch
from
c6268b5 to
3526b02
Compare
|
preview available: https://docs.tds.cscs.ch/47 |
|
preview available: https://docs.tds.cscs.ch/47 |
msimberg
changed the title
| ``` | ||
|
|
||
| A benefit of this approach is that the squashfs file can be copied to a location that is not subject to the Scratch cleaning policy. | ||
| Remember that virtual environments created by `uv` are relocatable only if the `--relocatable` option flag is passed to the `uv venv` command as mentioned in step 1. In that case, the generated environment is relocatable and thus it is possible to mount it in multiple locations without problems. |
There was a problem hiding this comment.
| Remember that virtual environments created by `uv` are relocatable only if the `--relocatable` option flag is passed to the `uv venv` command as mentioned in step 1. In that case, the generated environment is relocatable and thus it is possible to mount it in multiple locations without problems. | |
| Remember that virtual environments created by `uv` are relocatable only if the `--relocatable` flag is passed to the `uv venv` command as mentioned in step 1. In that case, the generated environment is relocatable and thus it is possible to mount it in multiple locations without problems. |
|
|
||
| Note that the original virtual environment is still installed in `$SCRATCH/sqfs-demo/.venv`, however the squashfs image has been mounted on top of it, so the single squashfs file is being accessed instead of the many files in the original version. | ||
|
|
||
| A benefit of this approach is that the squashfs file can be copied to a location that is not subject to the Scratch cleaning policy. |
There was a problem hiding this comment.
| A benefit of this approach is that the squashfs file can be copied to a location that is not subject to the Scratch cleaning policy. | |
| A benefit of this approach is that the squashfs file can be copied to a location that is not subject to the scratch cleaning policy. |
or
| A benefit of this approach is that the squashfs file can be copied to a location that is not subject to the Scratch cleaning policy. | |
| A benefit of this approach is that the squashfs file can be copied to a location that is not subject to the `$SCRATCH` cleaning policy. |
3 participants
No description provided.