@yacineMTB One use case is it's pretty important for certain kinds of architectures which otherwise produce high activations which disproportionately degrade training performance with lower precision training
@ZhaiAndrew Nice! I think I could really see myself using this but only if it works for all the entry points of finding saveable things that I already use, which is pretty much just apps
Just spent hours debugging a hanging distributed PyTorch job from accidentally having different dist.barrier() calls sync with each other... it was a good debugging lesson but also makes me think I should use barrier calls that are unique
@karpathy Out of curiosity, why fp16 over bfloat16 amp to start with? I would think bfloat16 amp would be slightly simpler to implement and a little more representative of what folks use nowadays afaik
@francoisfleuret Weight/gradient distributions (sometimes by layer) are helpful, especially if you know what to expect. Another thing for distributed training specifically (not always needed) is having rough consistency of local metrics across nodes
@EugeneVinitsky@frahs@jxmnop That plus the standard profiler run across batch sizes is gonna show a lot about which components see throughput improve with scale and which don’t.
@yohaniddawela This dataset is at least 1-2 orders of magnitude smaller than used for small foundation models in the generic image setting like clip. I guess fewer zero-shot tasks we care about means way less data is needed here? Any other thoughts on what's going on?