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

Document impact of the uniqueness constraint on memory footprint #1013

Open
antejavor opened this issue Oct 14, 2024 · 0 comments
Open

Document impact of the uniqueness constraint on memory footprint #1013

antejavor opened this issue Oct 14, 2024 · 0 comments
Assignees
@antejavor
Labels
priority: low (improvements) An idea how the representation of knowledge on a certain page could be improved

Comments

@antejavor
Copy link
Contributor

10 milion nodes with application ID = 1GB (approximately)
10 milion nodes with index on application ID = 2 GB (approximately)
10 milion nodes with a constraint on the application ID = 3GB (approximately)
Scaling this by a factor of 10:
100M nodes = 10GB
100M nodes + index = 20GB
100M nodes + index + constraint = 30GB
Scaling this by a factor of 10
1B = 100GB
1B nodes + index = 200GB
1B nodes + index + constraint = 300GB

Expand the memory calculation with the context on uniqueness constraints: https://memgraph.com/docs/fundamentals/storage-memory-usage#calculate-storage-memory-usage
@antejavor antejavor self-assigned this Oct 14, 2024
@katarinasupe katarinasupe added the priority: low (improvements) An idea how the representation of knowledge on a certain page could be improved label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@antejavor antejavor

Labels
priority: low (improvements) An idea how the representation of knowledge on a certain page could be improved
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@antejavor @katarinasupe