title: Neo4j Cypher queries really slow after upgrade to 2.1.3
body: <p>This morning, with some struggles (see: <a href="https://stackoverflow.com/questions/25240820/upgrading-a-neo4j-database-from-2-0-1-to-2-1-3-fails">Upgrading a neo4j database from 2.0.1 to 2.1.3 fails</a>), i upgraded my database from version 2.0.1 to 2.1.3. My main goal with the upgrade was to gain performance on certain queries (see: <a href="https://stackoverflow.com/questions/22557278/cypher-sort-performance">Cypher SORT performance</a>).</p>
  
  <p>Everything seems to be working, except for the fact that all Cypher queries - without exception - have become much, much, much slower. Queries that used to take 75ms now take nearly 2000ms.</p>
  
  <p>As i was running on an A1 (1xCPU ~2GB RAM) VM in Azure, i thought that giving neo4j some more ram and an extra core would help, but after upgrading to an A2 VM i get more or less the same results.</p>
  
  <p>I'm no wondering, did i loose my indexes by doing a backup and upgrading/using that db? I have perhaps 50K nodes in my db, so it's not that spectacular, right?</p>
  
  <p>I'm now still running on an A2 VM (2xCPU, ~4GB RAM), but had to downgrade to 2.0.1 again.</p>
  
  <hr>
  
  <p><strong>UPDATE: #1 2014-08-12</strong></p>
  
  <p>After reading Michael's first comment, on how to inspect my indexes using the shell, i did the following:</p>
  
  <ul>
  <li>With my 2.0.1 database service running (and performing well), i executed <code>Neo4jShell.bat</code> and then executed the <code>Schema</code> command. This yielded the following response:<img src="https://i.stack.imgur.com/BwouY.png" alt="enter image description here"></li>
  <li>I uninstalled the 2.0.1 service using the <code>Neo4jInstall.bat remove</code> command.</li>
  <li>I installed the 2.1.3 service using the <code>Neo4jInstall install</code> command.</li>
  <li>With my 2.1.3 database service running, I again executed the <code>Neo4jShell.bat</code> and then executed the <code>schema</code> command. This yielded the following response:<img src="https://i.stack.imgur.com/6k9O4.png" alt="enter image description here"></li>
  </ul>
  
  <p>I think it is safe to conclude that either the migration process (in 2.1.3) <em>or</em> the backup process (in 2.0.1) has removed the indexes from my database. This does explain why my backed up database is much smaller (~110MB) than the online database (~380MB). After migration to 2.1.3, my database became even smaller (~90MB).</p>
  
  <p>Question is now, is it just a matter of recreating my indexes and be done with it?</p>
  
  <hr>
  
  <p><strong>UPDATE: #2 2014-08-12</strong></p>
  
  <p>I guess i have answered my own question. After recreating the constraints and indexes, my queries perform like they used to (some even faster, as expected).</p>