You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2011/09/05 15:02:49 UTC

[Db-derby Wiki] Trivial Update of "InMemoryBackEndPrimer" by KristianWaagan

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "InMemoryBackEndPrimer" page has been changed by KristianWaagan:
http://wiki.apache.org/db-derby/InMemoryBackEndPrimer?action=diff&rev1=12&rev2=13

  The mechanisms to delete an in-memory database are:
  
   * restart the Java VM,
-  * drop database using connection ";drop=true" attribute.
+  * drop database using the ";drop=true" URL connection attribute.
  
  == Configuration and tuning ==
  The most important aspect to configure, is the size of the Java heap. When using the in-memory storage back end, the memory requirement should be similar to the memory requirements of using the disk-based storage back end plus the size of the user data. The general overhead will be increased somewhat.