It took me hours when I was creating indexes for a huge graph in Tigergraph, around hundred millions of nodes and edges, I wonder how Ultipa Graph handles it. Do you have similar issue with indexing?
Apply New License
License Detail
ID | |
Product | |
Status | |
Cores | |
Applied Validity Period(days) | |
Effective Date | |
Excpired Date | |
Mac Address | |
Apply Comment | |
Review Comment |
Account ID:
You have no license application record.
Certificate | Issued at | Valid until | Serial No. | File |
---|
Serial No. | Valid until | File |
---|
Not having one? Apply now! >>>
Product | Created On | ID | Amount (USD) | Invoice |
---|
Product | Created On | ID | Amount (USD) | Invoice |
---|
No Invoice
Sign In
Need an Ultipa account? Sign up now!
Already have an Ultipa account? Sign in now!
Back to sign in
It took me hours when I was creating indexes for a huge graph in Tigergraph, around hundred millions of nodes and edges, I wonder how Ultipa Graph handles it. Do you have similar issue with indexing?
1 Answer(s)
Greetings from Ultipa!
In all our released versions so far we haven't had such problems when creating indexes in huge graph like you mentioned. For sure creating index in huge graphs does cost disk space, but technically only the insertion operation might be affected a bi and the overall performance remains unaffected.
Ultipa Team