On Sat, Nov 21, 2009 at 11:35 AM, Laurent Laborde <[email protected]> wrote: > > My neo4j database won't be "critical" for the production, it can go > down and/or crash at anytime without breaking the production platform. > But... populating this database will take a lot of time and some > usefull ressource. So i'll try to not break it by using a too unstable > api :) > > I'm not 100% sure about the content of every node. But i think about a > few GB at minimum... up to hundred's of GB. > I'll see... it's a R&D project anyway. > But if it perform well and efficiently (i mean : faster and cheaper in > ressource than doing the same thing on our postresql cluster) the > database could be well over 100GB, not including FTS index that i'm > planning to use too :) > > I'm not 100% sure about what i'm doing here, that's all the fun of R&D. > Be sure that you will have as much feedback as possible as long as it > doesn't disclose the goals of the projects and the content of my > database (NDA, etc ...)
While i'm in vacation i have some times to play with neo. After some cleaning and testing, i'm finally populating the database with "real" data. My code is not 100% fail-safe, but the program that populate the database is running non-stop since 3 days, without a single error. The next step will be the exploitation of the content of the database. Neoclipse gave up a long time ago, i am expecting around 20.000 nodes and ... mmm... a million relationship (with different type) ? the database directory is currently 4.5GB ... i hope i didn't forgot a transaction somewhere that wrap everything and will rollback ~4GB of data if the program die :( i don't really understand the behaviour of the database if i have nested transaction. or what the database do if the program crash... it clean all un-finished transaction from DB, right ? Ho and ... Merry christmas :) -- Laurent "ker2x" Laborde Sysadmin & DBA at http://www.over-blog.com/ _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
