-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix] fix bugs when loading KV files and more. Also make horovod saving function is callable independent bug not patched origin save function. #364
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the perspective of software engineering, sincerely and strongly recommend that one commit fix only one minor problem to avoid introducing unexpected bugs
@@ -233,8 +233,7 @@ def _insert_de_shard_from_file_system( | |||
_values_tensor_dataset = readers.FixedLengthRecordDataset( | |||
shard_values_file_list, | |||
record_bytes=_value_dtype.size * value_dim, | |||
buffer_size=buffer_size * value_dim).padded_batch(insert_num_once * | |||
value_dim, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why here need to delete value_dim
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_values_tensor_dataset record_bytes is already _value_dtype.size * value_dim, if we padded_batch the bytes, they could be the size _value_dtype.size * value_dim * insert_num_once * value_dim. When they are reshaped, their shape would not compatible with _keys_tensor_dataset.
5a4dfb4
to
f4404dc
Compare
…set op, which could cause insert error.
… this time, as this can lead to unexpected errors. Now using de.keras.models.de_hvd_save_model to replace tf.keras.models.save_model.
…n, the recovered data will be the same first data in vector.
…estore parameter when using tf.train.Saver.
…nd is used to save DE KV files with different rank when using horovod all2all training.
…ger when using HvdAllToAllEmbedding by calling de.train.DEHvdCheckpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Functional Fix
Fix the default save function for tensorflow will not be patched at this time, as this can lead to unexpected errors.
Now using de.keras.models.de_hvd_save_model to replace tf.keras.models.save_model.
Bug Fix
New Feature
New Document
[doc] Add documentation for HvdAllToAllEmbedding.
Type of change
Checklist:
How Has This Been Tested?
Run the test.
But the fatal error in CPU table only happened in template <class K, class V, size_t DIM>, and I don't know how to trigger it in a small case.