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
Hi! Thanks for implementing --cache_latents_to_disk. It saves a lot of time as we don't need to use prepare_buckets_and_latents.py to save .npz files to disk, but instead we can save them directly when training.
However, I'm encountering a problem when using the --cache_latents_to_disk argument. The training takes longer time (it/s) than using the usual --cache_latents. Is this intended or a bug? Because, I thought that latent caching has its own process that is separate from the training.
Hi! Thanks for implementing
--cache_latents_to_disk
. It saves a lot of time as we don't need to useprepare_buckets_and_latents.py
to save.npz
files to disk, but instead we can save them directly when training.However, I'm encountering a problem when using the
--cache_latents_to_disk
argument. The training takes longer time (it/s
) than using the usual--cache_latents
. Is this intended or a bug? Because, I thought that latent caching has its own process that is separate from the training.Using
--cache_latents_to_disk
Using
--cache_latents
config_file.toml
: https://dpaste.com/B6AVPNK2K#Thank you!
The text was updated successfully, but these errors were encountered: