fix calculate_shard_storages to handle optimizer correctly #2652
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.
The parameter no longer possesses the
optimizer_class
attribute; instead, it has been updated tooptimizer_classes
. However, the current implementation of theEmbeddingStorageEstimator
still relies on the outdatedoptimizer_class
attribute to determine whether the parameter includes an optimizer. As a result, theEmbeddingStorageEstimator
fails to estimate the storage requirements for the optimizer, leading to CUDA out-of-memory errors during training.