DozerDB
Maximum number of nodes allowed to store #56
-
|
Do DozerDB removes the cap of number of nodes in community version? Is there a limit on how many nodes I can store in one database, and in one instance? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
DozerDB has not implemented higher formats yet because most use cases do not require it. The standard record format already supports around 34 billion nodes and relationships, which is far beyond what most use cases require. In practice, hardware resources (disk, RAM, CPU) will become the limiting factor long before those theoretical caps are reached. The high-limit record format simply sets aside more bits (I think it was 48 compared to 40 in the standard format), pushing the limits even higher. If there were ever a real-world need to exceed the standard format, adopting the high-limit format would be a straightforward change. |
Beta Was this translation helpful? Give feedback.
-
|
So, in DozerDB, every database can store around 34 billion nodes and relationships? Or every instance can store this many? |
Beta Was this translation helpful? Give feedback.
-
|
It should be per database, each one has its own storage space on disk, so the limit applies independently to every database you create. |
Beta Was this translation helpful? Give feedback.
DozerDB has not implemented higher formats yet because most use cases do not require it.
The standard record format already supports around 34 billion nodes and relationships, which is far beyond what most use cases require. In practice, hardware resources (disk, RAM, CPU) will become the limiting factor long before those theoretical caps are reached.
The high-limit record format simply sets aside more bits (I think it was 48 compared to 40 in the standard format), pushing the limits even higher.
If there were ever a real-world need to exceed the standard format, adopting the high-limit format would be a straightforward change.