You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been downloading select URLs from LAION-400M, -5B, and SBU and have noticed that there is a significant spike in RAM usage on startup that causes instances with <=32GB RAM, such as AWS' c6i.4xlarge, to crash. While img2dataset is running, however, RAM usage remains very low. I'd love if we could somehow mitigate that initial spike to be able to use instances with lower RAM throughout. Here's a screenshot from wandb.ai showing the initial spike on a 64GB instance:
The text was updated successfully, but these errors were encountered:
Here's another sample from a crashed c6i.4xlarge instance where we can see available process memory approach 0 before crashing:
Maybe the cause of the crashes is something else but I have not been able to run img2dataset on a c6i.4xlarge instance yet.
I've been downloading select URLs from LAION-400M, -5B, and SBU and have noticed that there is a significant spike in RAM usage on startup that causes instances with <=32GB RAM, such as AWS'
c6i.4xlarge
, to crash. Whileimg2dataset
is running, however, RAM usage remains very low. I'd love if we could somehow mitigate that initial spike to be able to use instances with lower RAM throughout. Here's a screenshot from wandb.ai showing the initial spike on a 64GB instance:The text was updated successfully, but these errors were encountered: