Replies: 1 comment 4 replies
-
Hm @luigidellaquila , AFAIK match queries always better than traverse queries or did I miss something? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I will describe some behavior I have with a 8 GB database ( 10 million nodes & 10 million edges ) that I cant explain myself ( OrientDB 3.0.34/Ubuntu/Java 8) . Xms=4gb,Xmx=12gb on a machine with 32 cores & 64gb ram
I am periodically executing something like 3 million traverse SQL query in OrientDB with a depth=4 by OrientDB HTTP API and getting the subgraph back
The biggest problem I have is random speed variations from 1 query per 5 minute to like 100 query per second. It goes like this:
5 minute I get 3 query/s .... after I can get 30query/s for 10m ......the 100/s for 20m ..then back to 0 query/s for a few minutes ..and so on
Thee query looks like this:
traverse * from (select * from Firma where cui="13990040") while ($depth <=4 and (@Class="Firma" or @Class="Persoana" or @Class="Actionar" or @Class="Administrator")) strategy BREADTH_FIRST
Its true the query can return sometimes a few hundred kb ..but usually returns just a few kb
Do you have any idea what should I try?
Thanks,
Mihai
Beta Was this translation helpful? Give feedback.
All reactions