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.

Sign up for GitHub

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

Jump to bottom

chainbase/mapped_usability.md: move uncommitted changes to RAM #70

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chainbase/mapped_usability.md: move uncommitted changes to RAM #70

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
987116e
Update mapped_usability.md
cc32d9 Aug 26, 2022
5cdf4f5
Merge branch 'eosnetworkfoundation:main' into main
cc32d9 Feb 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions chainbase/mapped_usability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,3 +24,6 @@ Obviously relying on undocumented behavior is yucky. But realistically the risk

This could be mitigated by including a fixed version of boost within chainbase. Something we've noodled on a little before and may be required for performance improvement in other proposal.

### use process RAM for uncommitted changes

Currently chainbase uses the mmap memory for everything, including uncommitted changes that are coming with speculative transactions. But the uncommitted changes don't have to be in the state memory, and it makes sense to store them in normal malloc memory. This would reduce the I/O load on the state storage significantly, so that we would probably not need tmpfs any longer.