Hi Fabrizio, It will be fixed tomorrow here is benchmarks of new implementation https://groups.google.com/forum/#!topic/orient-database/BSMippSCAFQ
On Tue, Feb 4, 2014 at 2:35 PM, Fabrizio Fortino <[email protected] > wrote: > Hi guys, > > I am doing some test with super-nodes on orientdb 1.6.4. > Basically I am trying to create a super-node with 3 million edges. > The insert performance becomes really slow after the first 50K edges (I am > using the OIntentMassiveInsert committing every 1000 records). > Moreover if I try select the super-node record from console the server > throws an OOM error. > > Any idea? > > Thanks, > Fabrizio > > On Saturday, February 18, 2012 3:47:32 PM UTC, bayoda wrote: > >> Hi >> >> Think as we tried both (not the commercial version of neo4j) - that the >> orientdb is ways faster. >> One of the best compareable things - Apache Licence / vs not really >> OpenSource >> >> Scaleability - running about 8 TB on OrientDB (actually Testing only >> inside the company) works (not one database - but several of them >> >> Development and Documentation - maybe neo4j is better >> >> Fixing and upgrades - orientdb clear winner ... >> >> stability - if you write some things wrong - every system crashes :-) >> >> greetings >> >> Michael >> >> 2012/2/18 Luca Garulli <[email protected]> >> >>> Hi Sergei, >>> I'm the wrong person to make this question :-) Probably it's better >>> asking it to someone used recent releases of both. >>> >>> Lvc@ >>> >>> On 18 February 2012 15:12, sergei <[email protected]> wrote: >>> >>>> thx lucas >>>> >>>> another question, sincerely how we could compare oriented vs neo4j ? >>>> what is better done in orientdb and better done in neo4j ? what about >>>> performances ? i know we have real documents in orientdb but i talk about >>>> efficiency, scalability and so on >>>> >>>> I guess this question is difficult but it should be a great help for me >>>> in my decision process >>>> >>>> thanks a lot >>>> >>>> >>>> 2012/2/17 Luca Garulli <[email protected]> >>>> >>>>> Hi, >>>>> since 1.0rc8 the references between vertexes and edges are managed by >>>>> a MVRB-Tree (the algorithm behind OrientDB indexes), so adding and >>>>> removing >>>>> edges impacts only the dirty tree nodes, not the entire tree. >>>>> >>>>> This only happens when the number of edges is major than a >>>>> configurable threshold (now as 8). >>>>> >>>>> Lvc@ >>>>> >>>>> >>>>> On 17 February 2012 20:25, sergei <[email protected]> wrote: >>>>> >>>>>> great >>>>>> common problems of super-node (traversal for example) are resolved ? >>>>>> >>>>>> >>>>>> 2012/2/17 Luca Garulli <[email protected]> >>>>>> >>>>>>> Hi Sergei, >>>>>>> the super-node problem has been fixed! >>>>>>> >>>>>>> By last benchmark adding the first or the millionth of edge takes >>>>>>> the same time. >>>>>>> >>>>>>> Lvc@ >>>>>>> >>>>>>> >>>>>>> On 17 February 2012 18:31, sergei fed <[email protected]> wrote: >>>>>>> >>>>>>>> hi >>>>>>>> >>>>>>>> >>>>>>>> it's been a while since my last seen of oriented. >>>>>>>> >>>>>>>> Super-node issue (dense node) are still a problem ? >>>>>>>> >>>>>>>> Thx >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >> >> -- >> bayoda.com - Professional Online Backup Solutions for Small and Medium >> Sized Companies >> > -- > > --- > 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/groups/opt_out. > -- Best regards, Andrey Lomakin. Orient Technologies the Company behind OrientDB -- --- 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/groups/opt_out.
