from http://docs.neo4j.org/chunked/milestone/indexing-batchinsert.html#indexing-batchinsert-best-practices :
- Try to avoid flushing<http://components.neo4j.org/neo4j/2.0.0/apidocs/org/neo4j/unsafe/batchinsert/BatchInserterIndex.html#flush%28%29> too often because each flush will result in all additions (since last flush) to be visible to the querying methods, and publishing those changes can be a performance penalty. Using a single threaded batch insertion, why would one flush index at all? (except for at the end of course) Why not just use the index, and only flush at the very end of the import? -- You received this message because you are subscribed to the Google Groups "Neo4j" 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.
