Hi guys, Lightweight edges are much faster than regular one. You can try a traversal with both and you'll see the difference. Things are different when indexing edges makes sense, so you could have better performance starting from edges.
Best Regards, Luca Garulli CEO at Orient Technologies LTD the Company behind OrientDB <http://orientdb.com> On 18 June 2015 at 09:24, Riccardo Tasso <[email protected]> wrote: > > 2015-06-17 21:55 GMT+02:00 W. Craig Trader <[email protected]>: >> >> With any database, when you have a non-trivial amount of data, you must >> must must consider how to tune the database, and part of tuning is creating >> and using appropriate indexes to support your queries. >> > > Yes, I am convinced of this statement. I was asking myself two important > modelling questions, which are not as trivial as I expected. > > First of all: in general are lightweight edges faster than regular edges > without properties? Benchmark answer is NO (for Orient >= 2.0.0). > > Second. if most of my queries involve typed edges (e.g. SELECT FROM V > WHERE out('type1').size() > 0) it is most efficient: > > - create many subclasses of E (and maybe indexing the property E.@CLASS > ) > - create a property E.type and then a index over it > > Anyway your suggestions were precious. I also discovered your very > interesting project for OrienDB benchmarking: I'm definitely interested in > looking into your use cases and maybe providing new ones. > > Cheers, > Riccardo > > -- > > --- > 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]. For more options, visit https://groups.google.com/d/optout.
