Skip to content

Add some information about the memory footprint of keeping a TypeDB database open #465

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
Open
alexjpwalker opened this issue Nov 26, 2020 · 2 comments
Open

Add some information about the memory footprint of keeping a TypeDB database open #465

alexjpwalker opened this issue Nov 26, 2020 · 2 comments
Labels
priority: medium type: documentation

Comments

@alexjpwalker
Copy link
Member

alexjpwalker commented Nov 26, 2020 •
edited by izmalk
Loading

We have observed that the TypeDB Java process consumes around 80MB of memory for each database that exists.

This is because it keeps all of its databases open at all times, to optimise I/O performance.

Information should be added to our docs that mentions this.
@izmalk
Copy link
Contributor

izmalk commented Jan 10, 2023

Is it still relevant and accurate?

@alexjpwalker
Copy link
Member Author

Yes, the above remains true today.

@izmalk izmalk changed the title Add some information about the memory footprint of keeping a Grakn database open Add some information about the memory footprint of keeping a TypeDB database open Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: medium type: documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexjpwalker @izmalk