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

Optional In-memory storage of all the data in current version #1

Open
kushti opened this issue Oct 14, 2016 · 2 comments
Open

Optional In-memory storage of all the data in current version #1

kushti opened this issue Oct 14, 2016 · 2 comments
Assignees
Milestone

Comments

@kushti
Copy link
Member

kushti commented Oct 14, 2016

Make a flag in database constructor to store all the data (current version only) in memory (guarantee is not needed, so if it is impossible to store the whole dataset in memory, dump it on disk anyway).

@jankotek jankotek added this to the 0.2 milestone Jan 12, 2017
@jankotek
Copy link
Contributor

Journal (last N updates) should be cached onheap. That also speed up Sharding Task, since it does not have to merge Journal

@jankotek
Copy link
Contributor

jankotek commented Nov 8, 2017

Memory mapped files in 0.5 should help it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants