Hi,
I have the following query:
select expand(out()) from #12:1231
1 item(s) found. Query executed in 8.638 sec(s).
and the explain command result is:
Profiled command
{
expandElapsed:0,
current: #12:1231,
fetchingFromTargetElapsed:0,
documentReads:1,
recordReads:1,
elapsed:0.464178,
resultType:collection,
resultSize:1
}
in 0.001000 sec(s):
{
expandElapsed:0,
current: #12:1231,
fetchingFromTargetElapsed:0,
documentReads:1,
recordReads:1,
elapsed:0.464178,
resultType:collection,
resultSize:1
}
With a database of ~4M vertices, 2 classes A and B (3M9 and 100k
correspondingly) and 3M9 . A has edges to B and one vertex in B can have
multiple edges coming from A.
I don't know why this query takes too much time.
Even a much more simpler query like:
select from #12:5487
1 item(s) found. Query executed in 1.655 sec(s).
I guess OrientDB doesn't have an index on RID, and each time I query using
RID, it does a full system scan.
Is there anyway to speed up this process? (I tried to index the RID but I
cannot do that)
Thank you in advance,
Hoan
--
---
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.
