Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Mon, 23 Mar 2009 11:22:27 -0000
Message-ID: <20090323112228.13054.7460@aurora.apache.org>
Subject: [Db-derby Wiki] 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 following page has been changed by KristianWaagan:
http://wiki.apache.org/db-derby/InMemoryBackEndPrimer

------------------------------------------------------------------------------
  [[BR]]
  
  Sizing the Derby page cache still impacts the performance when using the in-memory storage back end. The default value of ''1000'' pages should give acceptable performance for most basic applications, but it is not recommended that a smaller number of pages is specified. The data has to pass through the page cache even though the user data is already stored in main memory. A larger page cache may increase the performance at the cost of increased memory usage.
+ [[BR]]
+ 
+ To stop Derby from writing anything to ''derby.log'', see one of the ''derby.stream.error'' properties (for instance [http://db.apache.org/derby/docs/dev/ref/ref-single.html#rrefproper33027 derby.stream.error.field]).
  
  == Known limitations and bugs ==
  Know problems and issues will be listed in the table below.