Hi
We have started exploring OrientDB for building very lagre graphs (
cardinality of 1 million atleast) and most of the times we need
to use traverse command to cater our customers. Each node also comprises
some properties ( 10 to 12 properties) .
Would you please help us in addressing the following considerations to
move forward;
1. We are planning to use a 8 to 16 GB RAM machine , and our data per
day will be approximately 2GB, and we want to retain
3 days of data into system. So is a single machine capable enough
to scale with that data.
2. We get input data (event data) from a messaging platform as and
when event occurs, and we need to update the graph
with these messages. Can orientDB cope up with such frequent
updations ( may be 10 million messages a day). Do we need
stop and start the server as and when we update the underlying
graph, or is ot OK to update/modify (add a new vertex, edge) the graph
while the server is on.
3. What kind of indexes/clusters can be created so that queries can be
faster.
Regards
srinivas D
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
