-
Notifications
You must be signed in to change notification settings - Fork 273
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
Support serializing internal state #344
Comments
@Kixiron have you discovered any way to make this possible? I'm also interested—I would really love a DB that's like SQLite, but differential 😻 I wandered around the code base a bit, I'm not sure if it's possible without patching—or wrapping all the objects to log state because the timely-dataflow/timely/src/worker.rs Line 642 in 3671a3b
timely-dataflow/timely/src/progress/subgraph.rs Lines 39 to 70 in 79ff074
|
timely-dataflow/timely/src/worker.rs Line 214 in 3671a3b
|
Unfortunately not, my hopes are mostly in disk backed differential arrangements but I don't think there's much progress towards that |
Sameee, I would love that please — even just applying simple maps would be fine for me right now as well — not that the incremental is hard to write, but I would like to not, if I don't have to. Have you been exploring what it would take for what you're imagining? I'm wondering what would happen if I just started applying |
By and large it's a significantly more complex problem than just adding |
I'm working on a user-sided application with the goal of fast response times, and I've really been wanting a way to cache the internal state of dataflows so that it can be quickly recreated across restarts, enabling as fast of a restart time as possible while also skipping work that was already done in previous lifetimes of the program
The text was updated successfully, but these errors were encountered: