[orientdb] Oversize and edges

2014-01-24 Thread stefan
Hi, I'm persisting vertexes as append-only which will not be altered. In some cases edges might be added later for that that document (ACL). Is it good for me to set oversize=0 or does that in any way affect the creation of the new edges? Regards, - Stefan -- --- You received this message

Re: [orientdb] Oversize and edges

2014-01-24 Thread stefan
Hi, I have a potential use case where I have a very high number of edges (millions) for a document and I'm wondering if I should change them to one-directional links from the other site. Is there a practical limit to the number of edges for a vertex? (not theoretical) This is not a common

Re: [orientdb] Oversize and edges

2014-01-24 Thread Andrey Lomakin
Stefan, We are going to release first version of implementation of new relations in graphdb which is sometimes 20x (that is true) times faster than current one. Aslo data structure is used in this relations was tested by Kai Londenberg and he confirmed

Re: [orientdb] Oversize and edges

2014-01-24 Thread stefan
Thank you Andrey. Look forward to the changes are they in 1.7 SNAPSHOT already? It's good to know about the ~50 links and the separate data structure. Can I force the system to use the separate data structure after insert? (The reason I ask is that if I can then I can use oversize=0 and rely on

Re: [orientdb] Oversize and edges

2014-01-24 Thread Kai Londenberg
Hi, just a short question. Are you going to make that number (50) configurable ? It might make sense to set it to a lower number to get maximum performance. best, Kai Londenberg 2014/1/24 ste...@activitystream.com Thank you Andrey. Look forward to the changes are they in 1.7 SNAPSHOT

Re: [orientdb] Oversize and edges

2014-01-24 Thread Andrey Lomakin
Hi, Sure we have configurable upper and lower boundaries for conversions between embedded and sbtree based implementations, to avoid frequent conversions overhead between implementations during cases when you add 60 items and then remove 5. On Fri, Jan 24, 2014 at 3:05 PM, Kai Londenberg