Articles tagged as heap
Retired: Changing your Garbage Collection Method to G1
When to Use G1: By default, Neo4j versions 2.2 and earlier use Concurrent Mark and Sweep (CMS) for garbage collection. Customers with large heaps or who are seeing unacceptable garbage…
Enabling GC Logging
What is Garbage collection and why enabling it? A garbage collection event is a complete pause of the java application (ie: neo4j-server). It can be identified in the debug.log as…
Getting a JVM heap dump
This document provides the process of creating a heap-dump on a java machine to investigate potential memory leaks. Although a heap dump will be auto generated when OutOfMemoryError is thrown…
How do I configure init and max java heap when running bin/neo4j-backup
When running $NEO4J_HOME/bin/neo4j-backup if a Java out of heap/memory error occurs you may want define the init and max Java heap to be used by neo4j-backup. The default behavior is…
How to estimate initial memory configuration
The initial and eventual memory configuration parameters can be a moving target, based on how your store changes in size and how your workload increases or changes over time. This…
Large Delete Transaction Best Practices in Neo4j
In order to achieve the best performance, and avoid negative effects on the rest of the system, consider these best practices when processing large deletes. Start by identifying which situation…
Long GC Pauses caused by application code calling System.gc()
When investigating the cause of long garbage collection cycles, it is often useful to enable GC logging. You can do so by following the product documentation. Once this is enabled,…