This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new c1d3b9be4 Staged site from tdb-faqs
(4f05ec054eb1e6673fe0ba59878d079becc39cf8)
c1d3b9be4 is described below
commit c1d3b9be443ac6e7d664d4623b31dfe34bb9115a
Author: jenkins <[email protected]>
AuthorDate: Mon Feb 10 13:19:19 2025 +0000
Staged site from tdb-faqs (4f05ec054eb1e6673fe0ba59878d079becc39cf8)
---
content/documentation/tdb/faqs.html | 12 +++++++-----
content/index.json | 2 +-
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/content/documentation/tdb/faqs.html
b/content/documentation/tdb/faqs.html
index c0a775243..39fe69def 100644
--- a/content/documentation/tdb/faqs.html
+++ b/content/documentation/tdb/faqs.html
@@ -350,11 +350,13 @@ directory won’t be automatically removed unless the
compaction operation w
the immediate effect of a compaction may actually be more disk space usage
until the old data directory can be removed.
If the database was already maximally compacted then there will be no
difference in size between the old and new data
directories.</p>
-<p>We would recommend that you consider running a compaction after an initial
bulk data load. Also, if your database has
-ongoing updates over time we would also recommend that you consider running a
compaction periodically e.g. once a
-day/week etc. We cannot provide exact recommendations here as to the frequency
of compactions you should run as how much
-disk size inflation you experience will vary depending on many factors - size
and frequency of write transactions, data
-characteristics, etc. - and you will need to determine a suitable schedule
based on your use case for database.</p>
+<p>We would recommend that you consider running a compaction after an initial
bulk data load, although some bulk loading
+methods may already generate a maximally compacted database e.g. <a
href="#tdbloader-vs-tdbloader2"><code>tdbloader2</code></a>. Also, if
+your database has ongoing updates over time we would also recommend that you
consider running a compaction periodically
+e.g. once a day/week etc. We cannot provide exact recommendations here as to
the frequency of compactions you should run
+as how much disk size inflation you experience will vary depending on many
factors - size and frequency of write
+transactions, data characteristics, etc. - and you will need to determine a
suitable schedule based on your use case for
+database.</p>
<p>Note also that if running on Windows then it won’t be possible to
delete the old data directory due a OS limitation, see
<a href="#windows-dataset-delete">Why can’t I delete a dataset (MS
Windows/64 bit)?</a>.</p>
<h3 id="ssd">Should I use a SSD?</h3>
diff --git a/content/index.json b/content/index.json
index 3b96a36cf..c93b11beb 100644
--- a/content/index.json
+++ b/content/index.json
@@ -1 +1 @@
-[{"categories":null,"contents":"This page is historical \u0026ldquo;for
information only\u0026rdquo; - there is no Apache release of Eyeball and the
code has not been updated for Jena3.\nThe original source code is available. So
you\u0026rsquo;ve got Eyeball installed and you\u0026rsquo;ve run it on one of
your files, and Eyeball doesn\u0026rsquo;t like it. You\u0026rsquo;re not sure
why, or what to do about it. Here\u0026rsquo;s what\u0026rsquo;s going
on.\nEyeball inspects your model a [...]
\ No newline at end of file
+[{"categories":null,"contents":"This page is historical \u0026ldquo;for
information only\u0026rdquo; - there is no Apache release of Eyeball and the
code has not been updated for Jena3.\nThe original source code is available. So
you\u0026rsquo;ve got Eyeball installed and you\u0026rsquo;ve run it on one of
your files, and Eyeball doesn\u0026rsquo;t like it. You\u0026rsquo;re not sure
why, or what to do about it. Here\u0026rsquo;s what\u0026rsquo;s going
on.\nEyeball inspects your model a [...]
\ No newline at end of file
