huggingface / huggingface/setfit

Does anyone else get CUDA out of memory during hyperparameter search?

Open
#311 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
2.8k
Forks
267
Avg merge
36m
Merged PRs (30d)
5

Description

I had this problem and I see that in the repo's hyperparameter notebook someone else had this problem too! https://github.com/huggingface/setfit/blob/main/notebooks/text-classification_hyperparameter-search.ipynb

I fixed it by following this advice here https://github.com/huggingface/transformers/issues/13019

I wanted to make a pull request, but when I tried to reproduce the issue later (after pulling new changes) I couldn't. The memory use stayed constant over all the trials. Did e1a5375aa89c9f676319b82a44d16d7afc45e6e7 fix this? I'm curious. Would love to supply a PR if its helpful but maybe it's fixed already.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with notebooks/text-classification_hyperparameter-search.ipynb and compare its behavior with commit e1a5375aa89c9f676319b82a44d16d7afc45e6e7. Run the hyperparameter trials while monitoring memory, then determine whether CUDA out-of-memory still occurs and whether a reproducible change is needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
machine-learning, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.