I see where your coming from, but I'm expecting a lot of data, in the hundreds of millions, and my past experience has me leaning towards starting with performance in mind. I have joined in on too many projects where the project was designed with no expectation for significant growth and then suddenly became much more than it was originally intended.
On Thursday, March 12, 2015 at 11:52:12 AM UTC-4, Luigi Dell'Aquila wrote: > > Hi Jeffrey, > > I think you looked at this: > > > http://www.orientechnologies.com/docs/last/orientdb.wiki/Lightweight-Edges.html > > In terms of performance lightweight edges are better, but they are harder > to manage because: > - you cannot refer a lightweight edge by its RID (a lightweight edge is > not a document) > - a lightweight edge can become a regular edge (when you add properties), > so you never know if an edge is actually lightweight or if it's a regular > one, until you read it, so writing queries becomes more difficult > > More precisely: > 1) a regular edge is a document, so it takes space on disk as a normal > document. If you have number of edges much greater than number of vertices, > it can be significant > 2) you can work with lightweight edges but > - you never know if a lightweight edge is actually lightweight (until you > read it), because a lightweight edge can become a regular one during its > lifetime > - lightweight edges do not have a record id > 3) I prefer regular edges, I consider lightweight edges an optimization > > Luigi > > > > > > 2015-03-12 16:32 GMT+01:00 Jeffrey Auguste <[email protected] > <javascript:>>: > >> My understanding so far is that OrientDB has two type of Edges. Regular >> and Lightweight. The regular provides more flexibility and functionality at >> the cost of additional storage and performance. Its also my understanding >> that the lightweight edge is by default turned off with orientdb which >> makes it seem as though regular edges is the preferred over lightweight. >> >> So my questions are: >> 1. Is the difference in performance and/or storage significant with >> standard edges vs lightweight? If so, is it only affected in large >> databases? If so, what is considered Large? >> 2. The documentation states that Lightweight edges are hard to work with? >> If you agree, is it so difficult that you would question using them instead >> of regular edges? >> 3. Which do you prefer? In what situation would you switch to using the >> alternate edge to your preference? >> >> -- >> >> --- >> 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.
