I've just run the query with *explain* and the result is as follows: [image: o08YszH.png (1248×204)]
I've never used this before, but from what I have read here <https://code.google.com/p/orient/wiki/SQLExplain>, does the elapsed time means the query would take 51 seconds to execute?? On Friday, 24 April 2015 09:58:44 UTC+1, Luigi Dell'Aquila wrote: > > Hi, > > sorry for late answer, could you try an EXPLAIN? Just > > explain select * from Leaf > > it will give you more accurate information about query execution time and > execution plan > > Thanks > > Luigi > > > > > > 2015-04-23 17:57 GMT+02:00 cr0xfyre <[email protected] <javascript:>>: > >> Luigi? Anyone? >> >> >> On Tuesday, 21 April 2015 16:23:05 UTC+1, cr0xfyre wrote: >>> >>> Hi Luigi, >>> I'm looking at the output in the studio itself. Below the result table >>> it says something like: >>> "Query executed in 0.153 sec. Returned 20 record(s)" >>> >>> Isn't this time correct? if not, how can I see the real query time? >>> >>> On Tuesday, 21 April 2015 13:22:22 UTC+1, Luigi Dell'Aquila wrote: >>>> >>>> Hi cr0xfyre, >>>> >>>> how are you measuring these times? Are you reading the query EXPLAIN? >>>> I ask because this could be just the time Studio takes to render the >>>> results, a query like this should take a few tens milliseconds to execute. >>>> >>>> Luigi >>>> >>>> >>>> 2015-04-21 13:01 GMT+02:00 cr0xfyre <[email protected]>: >>>> >>>>> Hi everyone, >>>>> >>>>> I'm very new to orient (and DBs in general) and I know very little >>>>> about optimizing query speeds. >>>>> My problem right now is that a simple query like >>>>> >>>>> select * from Leaf >>>>> >>>>> is taking the following times, with different limits: >>>>> >>>>> >>>>> - *limit *= *time of query* >>>>> - 500 = ~0.7s >>>>> - 2450 = ~1.5s >>>>> - 3938 (max leafs right now) = ~2.4 s >>>>> >>>>> Some details: I'm running the queries in the studio. Leaf as only 6 >>>>> properties: a name (couple words max), a text (couple paragraphs), 2 >>>>> booleans and 2 dates. Leaf as also a couple different possible edges >>>>> connecting to it. >>>>> >>>>> Isn't this too much time for this simple query, or is it expected? 2.5 >>>>> seconds for only 4000 records seems like a lot when I'm expecting to have >>>>> 50k ou 100k of records in the future... >>>>> >>>>> Now, like I said, I'm very new to this and haven't applied any king of >>>>> optimization to my DB. Is this what indexes are for? how do they work and >>>>> how do I know which to apply? Are there any other ways to speed up >>>>> queries? >>>>> >>>>> Any help is welcome! >>>>> Thanks! >>>>> cr0xfyre >>>>> >>>>> -- >>>>> >>>>> --- >>>>> 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. >>>>> >>>> >>>> -- >> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- 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.
