dmarx / dmarx/Multi-Modal-Comparators
Gradient Checkpointing for OpenCLIP should be optional
Open
- Dominant language
- Jupyter Notebook
- Stars
- 39
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I know hardcoding it came from me but while Gradient Checkpointing makes things faster and use less VRAM so very useful on some use-cases, but can break things on A100 and also break `cutn_batches` on most text-to-image implementations, so ideally it should be optional for the user
More broadly we should think on how to load options that pertain to particular loaders/modules/perceptors while not breaking the overall mocking logics
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.