Hi all,
I've set up a pretty significant database in our evaluation of OrientDB. This means around four million edges on some 385,000 vertices. I'm trying to do some nifty document/property queries, but even if I boil them down to some bare essentials, I'm getting long query times, and my indices do not seem to be kicking in: SELECT count(*) FROM TYPE_A WHERE active // returns 139541, takes 1,2s // there is an index on "active" of type BOOLEAN SELECT count(*) FROM TYPE_A WHERE project_id = 14 // returns 46325, takes 1,2s // there is an index on "project_id" of type LONG Below is the essentials of the EXPLAIN, I think it shows that "projectionElapsed": 119, "groupByElapsed": 0, "current": "#18:195798", "evaluated": 195799, "fetchingFromTargetElapsed": 3920, "documentReads": 195799, "documentAnalyzedCompatibleClass": 195799, "recordReads": 195799, "elapsed": 3920.5286, "resultType": "collection", "resultSize": 1, "@fieldTypes": "projectionElapsed=l,groupByElapsed=l,current=x,evaluated=l,fetchingFromTargetElapsed=l,documentReads=l,documentAnalyzedCompatibleClass=l,recordReads=l,elapsed=f" The EXPLAIN also helpfully tells me: "*to speed up the execution, create an index or change the query to use an existent index*", although I believe that I already have the appropriate index set up. For reference: SELECT count(*) FROM TYPE_A // returns 195799, takes 0,148s (nice, fast!) Please! :) Your help would be much appreciated! Best regards, Sander. -- --- 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.
