Correction - disk size 116K is applicable only in failure cases. Here are the numbers for 100K node inserts (takes up 17MB):
4.0K active_tx_log 12K lucene 12K lucene-fulltext 4.0K neostore 4.0K neostore.id 884K neostore.nodestore.db 4.0K neostore.nodestore.db.id 2.4M neostore.propertystore.db 4.0K neostore.propertystore.db.arrays 4.0K neostore.propertystore.db.arrays.id 4.0K neostore.propertystore.db.id 4.0K neostore.propertystore.db.index 4.0K neostore.propertystore.db.index.id 4.0K neostore.propertystore.db.index.keys 4.0K neostore.propertystore.db.index.keys.id 13M neostore.propertystore.db.strings 4.0K neostore.propertystore.db.strings.id 4.0K neostore.relationshipstore.db 4.0K neostore.relationshipstore.db.id 4.0K neostore.relationshiptypestore.db 4.0K neostore.relationshiptypestore.db.id 4.0K neostore.relationshiptypestore.db.names 4.0K neostore.relationshiptypestore.db.names.id 4.0K nioneo_logical.log.active 4.0K tm_tx_log.1 17M total On Tue, Jun 1, 2010 at 6:50 PM, Biren Gandhi <[email protected]> wrote: > While trying to perform a create-only stress test for nodes, i'm constantly > getting Out of Memory error even while running with these params (with > default config - as no searching/optimizations are being exercised just > yet): > > EXTRA_JVM_ARGUMENTS="-d64 -server -Xms256m -Xmx1024m" > > Able to create 200K nodes (without any attributes - bare bone nodes only) > successfully, but anything above that Java gives up. One strange observation > is that the disk size gets capped at 116K in all of the cases while tying to > create 100K, 200K, 300K nodes on a fresh DB. > > Is there any limit on number of nodes that can be created in a neo4j > instance? Any other tips? > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
