Database Reference
In-Depth Information
The following screenshot showstheinalresultofLoadCSV:
From working with the Load CSV toolset at this early milestone release, it seems clear
that there are still quite a few things to iron out, but in general, we still recommend
that you take a look at it as it presents you with a very intuitive and native way of
importing data into Neo4j. Neo Technology also claims that this approach should work
well for imports into millions (but not billions) of nodes and relationships, especially
if you want to make use of the periodic commit functionality that is tied to Load CSV.
If you start your Load CSV statements with a "using periodic commit {a number}",
Neo4j will periodically commit your import transactions, thereby making it a lot
easier to scale your import.
Foralargerimportusecase,wewillnowtakealookatainaldataimporttoolset.
Scaling the import
Many users of Neo4j need to import larger datasets into Neo4j, at least for their initial
startupusecases.Doingsocanbedificultusinganyoftheprevioustechniquesand
takes a long time. Although there are a number of things that you can tweak (for
example, the batch sizes in Neo4j-shell-tools), there is a limit to the transactional
write performance that you will get from running the Neo4j server. This limit is mostly
I/OdrivenbecauseofthetransactionalqualitiesoftheNeo4jdatabasemanagement
system; it basically needs to go down to disk at every commit and can take some time.
 
Search WWH ::




Custom Search