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

[Feature]automatic saving #861

Open
shouldsee opened this issue Sep 1, 2022 · 2 comments
Open

[Feature]automatic saving #861

shouldsee opened this issue Sep 1, 2022 · 2 comments

Comments

@shouldsee
Copy link
Contributor

shouldsee commented Sep 1, 2022

Dear author,

Thank you for creating and sharing this fabulous tool!

Is your feature request related to a problem? Please describe.
Ex. I'm always frustrated when Visdom crashed and all my data lost. current solutions call vis.save to create json snapshots but this sounds expensive.

Describe the solution you'd like

  • Automatically saving env data to disk on a incremental basis.. when I call vis.scatter to create a plot, the server writes the received data
    immediately to disk.
  • alternatively, server caches data on a periodically basis.
  • open to discuss whether it should be immediate or periodic

Describe alternatives you've considered
Not sure what's the best impl yet.

@shouldsee shouldsee changed the title refactoring the data model to enable automatical saving [Feature]refactoring the data model to enable automatical saving Sep 1, 2022
@shouldsee shouldsee changed the title [Feature]refactoring the data model to enable automatical saving [Feature]automatic saving Sep 1, 2022
@JackUrb
Copy link
Contributor

JackUrb commented Sep 1, 2022

Hi @shouldsee - you may be interested in the log_to_filename argument, which automatically logs all outgoing plots to a file such that the log can be replayed later if the server crashes.

@shouldsee
Copy link
Contributor Author

Hi @shouldsee - you may be interested in the log_to_filename argument, which automatically logs all outgoing plots to a file such that the log can be replayed later if the server crashes.

Sounds cool. This is essentially a transaction log stored to the file. I am more interested in the stateful persistent storage.

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

2 participants