Skip to content
This repository has been archived by the owner on Jun 17, 2022. It is now read-only.

State persistence #32

Closed
mappum opened this issue Nov 16, 2017 · 1 comment
Closed

State persistence #32

mappum opened this issue Nov 16, 2017 · 1 comment

Comments

@mappum
Copy link
Contributor

mappum commented Nov 16, 2017

Currently, the state is only held in memory, so a full chain replay is done every time a node starts up. It's possible to persist the state in a way that doesn't break the synchronous app handler APIs, we just need to flush the changes to disk in between each block.
@mappum mappum changed the title State Persistence State persistence Nov 16, 2017
@keppel
Copy link
Owner

keppel commented Jan 15, 2019

Done

@keppel keppel closed this as completed Jan 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mappum @keppel