Memory constrains graph size, disk I/O constrains read/write performance, as always.
Performance is generally memory or I/O bound for large graphs, and compute bound for graphs which fit in memory.
More memory allows even larger graphs, but runs the risk of inducing larger Garbage Collection operations.
Aside from capacity, the performance characteristics of the disk are the most important when selecting storage.
For proper ACID behavior, the filesystem must support flush (fsync, fdatasync).
The Neo4j runtime is continuously tested with
Copyright © 2012 Neo Technology