Building a Graph Database Application - Graph Databases - page 96

The Neo4j documentation includes details of the size of records and
objects that we can use in our calculations. For more general perfor‐
mance and tuning tips, see this site .
Figure 4-11. Cost versus performance trade-offs
In optimizing a graph database solution for performance, we should bear in mind the
following guidelines:
• We should utilize the filesystem cache as much as possible; if possible, we should
map our store files in their entirety into this cache
• We should tune the JVM heap and keep an eye on GC behaviors
• We should consider using fast disks—SSDs or enterprise flash hardware—to bring
up the bottom line when disk access becomes inevitable
Redundancy
Planning for redundancy requires us to determine how many instances in a cluster we
can afford to lose while keeping the application up and running. For non-business-
critical applications, this figure might be as low as one (or even zero); once a first instance
has failed, another failure will render the application unavailable. Business-critical