4 ms·

hmm -- I tried converting to float16 just using a naive model.half() call and saw some quality degradation in my images compared to just autocasting parts of th

by mkaic 4y ago

hmm -- I tried converting to float16 just using a naive model.half() call and saw some quality degradation in my images compared to just autocasting parts of the model to float16 while leaving others at float32. Curious if anyone else has had the same experience.

zone411 4y ago
You may want to try bfloat16 instead.
naillo 4y ago
Might be that there's some degredation but I think it's pretty close. Anyway I'm using their 'official' fp16 version which they might be doing some extra magic on idk. I.e. via StableDiffusionPipeline.from_pretrained("CompVis/stable-diffusion-v1-4", revision="fp16", torch_dtype=torch.float16, ...)
- butwhywhyoh 4y ago
  But you just said "no degradation".
  - naillo 4y ago
    Try it yourself ;) I haven't spotted any but I can't dispute the parents observations.
    - mkaic 4y ago
      My best guess is that I just did something wrong lol. Autocast seems to convert most of the model to fp16 anyways and that works great, so I'll just keep using that!
- fomine3 4y ago
  Can I download ckpt file for fp16?