Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Left-over data for BlueFog optimizers using num_step_per_communication #65

Open
hanbinhu opened this issue Dec 29, 2020 · 0 comments
Open

Left-over data for BlueFog optimizers using num_step_per_communication #65

hanbinhu opened this issue Dec 29, 2020 · 0 comments
Assignees
@hanbinhu @BichengYing
Labels
investigation This issues requires more investigation

Comments

@hanbinhu
Copy link
Collaborator

When the batch_size cannot be exactly divided by num_step_per_communication in the BlueFog optimizers, each epoch will leave some data to the next epoch for communication, which may result in a model not fully using the entire dataset in the last epoch. In addition, the mixed data usage between adjacent epochs is also not desired.
@hanbinhu hanbinhu added the investigation This issues requires more investigation label Dec 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hanbinhu hanbinhu

@BichengYing BichengYing

Labels
investigation This issues requires more investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hanbinhu @BichengYing