1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
This is being tracked in the GitHub issue linked below.
A possible workaround is to use a regular Notebook Instance instead of a Studio Notebook Instance. On a regular Notebook Instance of the same size (ml.g4dn.xlarge), /dev/shm is 7.7G
df -h | grep -E 'shm|File'
Filesystem Size Used Avail Use% Mounted on
tmpfs 7.7G 0 7.7G 0% /dev/shm
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 6 mesi fa
- AWS UFFICIALEAggiornata un anno fa
Are you using PyTorch with the SageMaker Python SDK (as described here: https://sagemaker.readthedocs.io/en/stable/frameworks/pytorch/using_pytorch.html) or are you bringing your own code to the SageMaker environment (as described here: https://sagemaker.readthedocs.io/en/stable/frameworks/pytorch/using_pytorch.html#bring-your-own-model)?