title: Neo4J Memory tuning having little effect
body: <p>I am currently running some simple cypher queries (count etc) on a large dataset (>10G) and am having some issues with tuning NE04J. </p>
  
  <p>The machine running the queries has 4TB of ram, 160 cores and is running Ubuntu 14.04/neo4j version 2.3. Originally I left all the settings as default as it is stated that free memory will be dynamically allocated as required. However, as the queries are taking several minutes to complete I assumed this was not the case. As such I have set various combinations of the following parameters within the neo4j-wrapper.conf:</p>
  
  <pre><code>wrapper.java.initmemory=1200000 
  wrapper.java.maxmemory=1200000
  dbms.memory.heap.initial_size=1200000
  dbms.memory.heap.max_size=1200000
  dbms.jvm.additional=-XX:NewRatio=1
  </code></pre>
  
  <p>and the following within neo4j.properties:</p>
  
  <pre><code>use_memory_mapped_buffers=true
  neostore.nodestore.db.mapped_memory=50G
  neostore.relationshipstore.db.mapped_memory=50G
  neostore.propertystore.db.mapped_memory=50G
  neostore.propertystore.db.strings.mapped_memory=50G
  neostore.propertystore.db.arrays.mapped_memory=1G
  </code></pre>
  
  <p>following every guide/Stackoverflow post I could find on the topic, but I seem to have exhausted the available material with little effect. </p>
  
  <p>I am running queries through the shell using the following command <code>neo4j-shell -c &lt; "queries/$1.cypher"</code>, but have also tried explicitly passing the conf files with <code>-config $NEO4J_HOME/conf/neo4j-wrapper.conf</code> (restarting the sever everytime I make a change).</p>
  
  <p>I imagine that I have missed something silly which is causing the issue, as there are many reports of neo4j working well with data of this size, but cannot think what it could be. As such any help would be greatly appreciated. </p>