Remove lr scheduler in DeepSpeed config to avoid conflict #909
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removed the following
schduler
in DeepSpeed config files.The
scheduler
in DeepSpeed configurations is not necessary because the axolotl package defines its own learning rate scheduler (which is passed to the HuggingFace trainer). In fact, the DeepSpeed scheduler can sometimes cause conflicts. For instance, when lr_scheduler: constant_with_warmup is set in the training YAML file, the actual scheduler is overridden by DeepSpeed'sscheduler
(which is DeepSpeed'sWarmupDecayLR
instead of HuggingFace'sconstant_with_warmup
). Removingscheduler
from DeepSpeed configurations can resolve this issue.