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.

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

The sync_cycle concept is confusing. Can we switch to use a timer? #326

Closed
jetfuel opened this issue Mar 15, 2018 · 1 comment
Closed

The sync_cycle concept is confusing. Can we switch to use a timer? #326

jetfuel opened this issue Mar 15, 2018 · 1 comment
Assignees

Comments

@jetfuel
Copy link
Collaborator

jetfuel commented Mar 15, 2018

sync_cycle is used to determine how often the VisualDL should persist data into the filesystem. Without extensive documentation, our users won't be able to understand how to choose a proper sync_cycle value to see the real-time Scalar update without impacting the training performance.

We should try some different approach to trigger the PersistToDisk(). For example, VisualDL can set a timer of 30 seconds, and it will call PersistToDisk() when the countdown ends.

@jetfuel jetfuel self-assigned this Mar 15, 2018
@jetfuel
Copy link
Collaborator Author

jetfuel commented Mar 20, 2018

We could just avoid exposing the variable all together. and make the sync_cycle to adjust itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant