Author: buildbot
Date: Thu Jun 19 09:51:48 2014
New Revision: 913000
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/tdb/faqs.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 19 09:51:48 2014
@@ -1 +1 @@
-1603796
+1603798
Modified: websites/staging/jena/trunk/content/documentation/tdb/faqs.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tdb/faqs.html (original)
+++ websites/staging/jena/trunk/content/documentation/tdb/faqs.html Thu Jun 19
09:51:48 2014
@@ -204,7 +204,7 @@ database to be overwritten.</p>
<p>TDB uses memory mapped files heavily for providing fast access to data and
indices. Memory mapped files live outside of the JVM heap and are managed by
the OS therefore it is important to not allocate all available memory to the
JVM heap.</p>
<p>However JVM heap is needed for TDB related things like query & update
processing, storing the in-memory journal etc and also for any other activities
that your code carries
-out. What you should see the JVM heap to will depend on the kinds of queries
that you are running, very specific queries will not need a large heap whereas
queries that touch
+out. What you should set the JVM heap to will depend on the kinds of queries
that you are running, very specific queries will not need a large heap whereas
queries that touch
large amounts of data or use operators that may require lots of data to be
buffered in-memory e.g. <code>DISTINCT</code>, <code>GROUP BY</code>,
<code>ORDER BY</code> may need a much larger heap depending
on the overall size of your database.</p>
<p>There is no hard and fast guidance we can give you on the exact number
since it depends heavily on your data and your workload. Please ask on our
mailing lists
