You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a project in which we are thinking to use nebula graph database to represent the file system of different cloud systems of our clients. Initially, we have thought to use one graph space for one cloud storage with 1 partition count as we think meta information of a file system will be able to store on a single machine. A client can have many cloud storages - say 100. And we want to scale to about 1000 clients. Will nebula graph be able to scale graph spaces to 100,000? The reason for this decision to keep the latency low for traversal queries so that query doesn't need to span multiple nodes.
I do see in the documentation that it uses multi-group raft in storaged layer that share resources like in transport layer and thread pool. But still I would like to know some expert's opinion before taking this decision.
The other option is to setup graph spaces at the client level and keeping a higher partition count than 1.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi All,
We have a project in which we are thinking to use nebula graph database to represent the file system of different cloud systems of our clients. Initially, we have thought to use one graph space for one cloud storage with 1 partition count as we think meta information of a file system will be able to store on a single machine. A client can have many cloud storages - say 100. And we want to scale to about 1000 clients. Will nebula graph be able to scale graph spaces to 100,000? The reason for this decision to keep the latency low for traversal queries so that query doesn't need to span multiple nodes.
I do see in the documentation that it uses multi-group raft in storaged layer that share resources like in transport layer and thread pool. But still I would like to know some expert's opinion before taking this decision.
The other option is to setup graph spaces at the client level and keeping a higher partition count than 1.
Beta Was this translation helpful? Give feedback.
All reactions