title: MemSQL and H2 comparison
body: <p>I am considering moving from H2 to MemSQL - and I would greatly appreciate any comments:</p>
  
  <p>My application has to query very quickly concurrently from large tables of up to 300Million rows. To achieve this I have been using the H2 in-memory database. </p>
  
  <p>I'm currently using the H2 database which allows me to create linked tables in the H2 in-memory database that point to a MySQL database. This is very useful in loading data from MySQL to H2. </p>
  
  <p>Can I create Linked tables in MemSQL - I see no references to this in the online MemSQL documentation?</p>
  
  <p>Another challenge is that I will need to run multiple instances of the application across many servers, so having MemSQL running distributed across servers is very attractive rather than having to duplicate the H2 database in every JVM instance of the application across the servers. Running one instance of H2 via TCP to the other servers will be too slow.</p>
  
  <p>The other advantage I see with MemSQL is that there is apparently no locking and the queries are compiled into native C++ which could speed them up.</p>
  
  <p>Has anyone compared MemSQL performance with H2? - I've found nothing on line from real world tests.</p>