artifacts do not clean .cache after upload
See original GitHub issuewandb --version && python --version && uname
- Weights and Biases version: 0.9.4
- Python version: 3.6.10
- Operating System: Win 10
Description
Artifacts upload in wandb runs doesn’t seem to clean up cache files after itself properly.
As I work with my ML experiments, the C:\Users\<Username>\.cache\wandb\artifacts
folder grows up to the point that it exhausts all the free space on my drive (up to 50 Gb). After this point, I have to clean it manually to resume my work.
The size of all artifacts to be uploaded within a single run is about 5Gb (counting all the versions of the same files), which is definitely less that the .cache folder size when I discover the problem
Additional errors
At times I get these errors at the end of the run:
C:\ProgramData\Anaconda3\lib\site-packages\wandb\compat\tempfile.py:64: UserWarning: Couldn't remove temp directory C:\Users\Maria\AppData\Local\Temp\tmp7apg1zqmwandb
_warnings.warn("Couldn't remove temp directory %s" % name)
C:\ProgramData\Anaconda3\lib\site-packages\wandb\compat\tempfile.py:64: UserWarning: Couldn't remove temp directory C:\Users\Maria\AppData\Local\Temp\tmpxa113_1ewandb-media
_warnings.warn("Couldn't remove temp directory %s" % name)
C:\ProgramData\Anaconda3\lib\site-packages\wandb\compat\tempfile.py:64: UserWarning: Couldn't remove temp directory C:\Users\Maria\AppData\Local\Temp\tmpghqvixfewandb
_warnings.warn("Couldn't remove temp directory %s" % name)
c:\programdata\anaconda3\lib\site-packages\wandb\compat\tempfile.py:64: UserWarning: Couldn't remove temp directory C:\Users\Maria\AppData\Local\Temp\tmpx0vikdffwandb-media
_warnings.warn("Couldn't remove temp directory %s" % name)
c:\programdata\anaconda3\lib\site-packages\wandb\compat\tempfile.py:64: UserWarning: Couldn't remove temp directory C:\Users\Maria\AppData\Local\Temp\tmpit2fs8f5wandb
_warnings.warn("Couldn't remove temp directory %s" % name)
Which seems related to cleaning-up but point to a different Temp folder that DO NOT have this problem of size growing
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
artifacts do not clean .cache after upload · Issue #1193
Artifacts upload in wandb runs doesn't seem to clean up cache files after itself properly. As I work with my ML experiments, the...
Read more >caches vs artifacts
After completing successfully, the step will upload the contents of ~/.m2 as the maven cache. Step 2 has not configured any caches. And...
Read more >Artifacts (local) caching - how does it really work? - W&B Help
My first question is: if I run the code twice (on the same machine), will the model-weights be downloaded again or are they...
Read more >Caching in GitLab CI/CD
Cache is stored where GitLab Runner is installed and uploaded to S3 if distributed cache is enabled. Use artifacts to pass intermediate build...
Read more >Artifactory Cleanup Best Practices
The Cleanup Unused Cached Artifacts field will, by default, execute a cache cleanup once every day. Deleting Unused Artifacts. Artifactory will ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @maria-korosteleva,
I had the same problem and was able to change the cache directory to another drive available to me. If that’s an option for you, look into setting the environment variable
WANDB_CACHE_DIR
(see code here).Issue-Label Bot is automatically applying the label
bug
to this issue, with a confidence of 0.89. Please mark this comment with 👍 or 👎 to give our bot feedback!Links: app homepage, dashboard and code for this bot.