Author: rvesse
Date: Thu Jun 19 09:51:39 2014
New Revision: 1603798
URL: http://svn.apache.org/r1603798
Log:
Fix minor typo
Modified:
jena/site/trunk/content/documentation/tdb/faqs.mdtext
Modified: jena/site/trunk/content/documentation/tdb/faqs.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tdb/faqs.mdtext?rev=1603798&r1=1603797&r2=1603798&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tdb/faqs.mdtext (original)
+++ jena/site/trunk/content/documentation/tdb/faqs.mdtext Thu Jun 19 09:51:39
2014
@@ -74,7 +74,7 @@ TDB uses memory mapped files heavily for
the OS therefore it is important to not allocate all available memory to the
JVM heap.
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. `DISTINCT`, `GROUP BY`, `ORDER BY` may need a much
larger heap depending
on the overall size of your database.
