switch cosmic-swingset to use LMDB for kernel storage #899
Labels
cosmic-swingset
package: cosmic-swingset
Comments
warner
added a commit
that referenced
this issue
Apr 9, 2020
We were still using swing-store-simple, which keeps the kernel state in RAM. This is serialized to disk at the end of each block. This switches it to our nice shiny swing-store-lmdb, which keeps the state on disk at all times, only reading one key at a time into RAM. closes #899
warner
added a commit
that referenced
this issue
Apr 9, 2020
We were still using swing-store-simple, which keeps the kernel state in RAM. This is serialized to disk at the end of each block. This switches it to our nice shiny swing-store-lmdb, which keeps the state on disk at all times, only reading one key at a time into RAM. closes #899
warner
added a commit
that referenced
this issue
Apr 9, 2020
We were still using swing-store-simple, which keeps the kernel state in RAM. This is serialized to disk at the end of each block. This switches it to our nice shiny swing-store-lmdb, which keeps the state on disk at all times, only reading one key at a time into RAM. closes #899
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've made progress on #513 to move kernel state out of RAM and into a disk-based database. But it looks like we haven't deployed that into cosmic-swingset yet:
agoric-sdk/packages/cosmic-swingset/lib/launch-chain.js
Line 14 in d33a791
Thanks to @FUDCo 's hard work, the fix should be as simple as changing that line to import from
@agoric/swing-store-lmdb(and updatingpackage.jsonto depend upon it)The same needs to be done for ag-solo, in
lib/ag-solo/reset-state.jsandlib/ag-solo/start.js.The text was updated successfully, but these errors were encountered: