Hi Massimo, It's too bad you are running into the same kind of situations, (specially when the conclusion you came up to is that Neo4j just degrades...). However, did you already try dividing "the" big insertion process into smaller steps? I mean, do you think Neo4j degradation is just proportional to DB size ? or rather just to the amount of data being inserted in the same Batch Insertion? Cheers,
Pablo On Thu, Feb 17, 2011 at 12:44 PM, Massimo Lusetti <[email protected]>wrote: > On Wed, Feb 16, 2011 at 11:12 AM, Mark Harwood <[email protected]> > wrote: > > > However, the underlying Neo4J database doesn't seem to be able to cope > > with inserting these volumes of data on my available hardware and I > > don't have (and would hope not to need) 10s of gigabytes of RAM to > > throw at the problem. > > I'm using different data (see other threads) but this seems the same > situations I've been running into... Neo4J degrade performance as soon > as the db grows in size and it can't finish the work. > > Cheers > -- > Massimo > http://meridio.blogspot.com > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Pablo Pareja Tobes LinkedIn http://www.linkedin.com/in/pabloparejatobes Twitter http://www.twitter.com/pablopareja http://about.me/pablopareja http://www.ohnosequences.com _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
