Is there any general recommendation how to speed up queries?
My query is
select count(*) from V where class_name = 'VicClet' AND Deleted = 0 AND
DocNumber = '-222-PP'
I have about 500 000 vertices and this query returns about 50 000, but it
lasts about 15 secs! Where is that speed that
Hi Bojan
can you post the explain of the query?
Enrico
2014-10-24 15:00 GMT+02:00 BojanV bboojja...@gmail.com:
Is there any general recommendation how to speed up queries?
My query is
select count(*) from V where class_name = 'VicClet' AND Deleted = 0 AND
DocNumber = '-222-PP'
I
I have following situation:
I am importing my rdbms to OrientDB. That's my first problem with
performance - creation of vertices is ok, but creating of edges is
extremely slow. I tried a few cases: to put vertices in separate class, to
use default class (V), to use ETL but no significant
Hi,
no, M2 is not the latest snapshot.
You can find it here
https://oss.sonatype.org/content/repositories/snapshots/com/orientechnologies/orientdb-community/2.0-SNAPSHOT/
Luigi
2014-10-21 21:15 GMT+02:00 Kanak Agarwal agarwal.ka...@gmail.com:
Hi
Thanks for the response. I am seeing the
Hi,
what version of OrientDB are you using? We had two issues related to OR
operators and index usage:
https://github.com/orientechnologies/orientdb/issues/2898
https://github.com/orientechnologies/orientdb/issues/2893
and we fixed them some days ago.
Could you try again on latest SNAPSHOT?
Hi
Thanks for the response. I am seeing the issue in the OrientDB 2.0-M2
community edition.
Is this the latest SNAPSHOT?
On Tuesday, October 21, 2014 2:23:04 AM UTC-5, Luigi Dell'Aquila wrote:
Hi,
what version of OrientDB are you using? We had two issues related to OR
operators and
Hello
My V class contains two properties prop1 and prop2 both of which are
indexed using non unique hash index.
The queries on prop1 alone (select from V where prop1 = 'xyz') or prop2
alone (select from V where prop1 = 'abc') use the index and perform well.
On the other hand, a query that uses
