doc and web perf notes
This commit is contained in:
@@ -18,10 +18,10 @@ names. The list in the default configuration does not exclude hidden
|
||||
directories (names beginning with a dot), which means that it may index
|
||||
quite a few things that you do not want. On the other hand, email user
|
||||
agents like Thunderbird usually store messages in hidden directories, and
|
||||
you probably want this indexed. One possible solution is to have '.*' in
|
||||
'skippedNames', and add things like '~/.thunderbird' '~/.evolution' to
|
||||
'topdirs'. Not even the file names are indexed for patterns in this
|
||||
list, see the 'noContentSuffixes' variable for an alternative approach
|
||||
you probably want this indexed. One possible solution is to have ".*" in
|
||||
"skippedNames", and add things like "~/.thunderbird" "~/.evolution" to
|
||||
"topdirs". Not even the file names are indexed for patterns in this
|
||||
list, see the "noContentSuffixes" variable for an alternative approach
|
||||
which indexes the file names. Can be redefined for any
|
||||
subtree.</para></listitem></varlistentry>
|
||||
<varlistentry id="RCL.INSTALL.CONFIG.RECOLLCONF.NOCONTENTSUFFIXES">
|
||||
@@ -366,10 +366,11 @@ which lets Xapian perform its own thing, meaning flushing every
|
||||
$XAPIAN_FLUSH_THRESHOLD documents created, modified or deleted: as memory
|
||||
usage depends on average document size, not only document count, the
|
||||
Xapian approach is is not very useful, and you should let Recoll manage
|
||||
the flushes. The default value of idxflushmb is 10 MB, and may be a bit
|
||||
low. If you are looking for maximum speed, you may want to experiment
|
||||
with values between 20 and
|
||||
80. In my experience, values beyond 100 are always counterproductive. If
|
||||
the flushes. The program compiled value is 0. The configured default
|
||||
value (from this file) is 10 MB, and will be too low in many cases (it is
|
||||
chosen to conserve memory). If you are looking
|
||||
for maximum speed, you may want to experiment with values between 20 and
|
||||
200. In my experience, values beyond this are always counterproductive. If
|
||||
you find otherwise, please drop me a note.</para></listitem></varlistentry>
|
||||
<varlistentry id="RCL.INSTALL.CONFIG.RECOLLCONF.FILTERMAXSECONDS">
|
||||
<term><varname>filtermaxseconds</varname></term>
|
||||
|
||||
@@ -20,8 +20,8 @@ alink="#0000FF">
|
||||
<div class="titlepage">
|
||||
<div>
|
||||
<div>
|
||||
<h1 class="title"><a name="idp41214976" id=
|
||||
"idp41214976"></a>Recoll user manual</h1>
|
||||
<h1 class="title"><a name="idp9509520" id=
|
||||
"idp9509520"></a>Recoll user manual</h1>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
@@ -109,13 +109,13 @@ alink="#0000FF">
|
||||
multiple indexes</a></span></dt>
|
||||
|
||||
<dt><span class="sect2">2.1.3. <a href=
|
||||
"#idp46788704">Document types</a></span></dt>
|
||||
"#idp41562832">Document types</a></span></dt>
|
||||
|
||||
<dt><span class="sect2">2.1.4. <a href=
|
||||
"#idp46808384">Indexing failures</a></span></dt>
|
||||
"#idp41582512">Indexing failures</a></span></dt>
|
||||
|
||||
<dt><span class="sect2">2.1.5. <a href=
|
||||
"#idp46815840">Recovery</a></span></dt>
|
||||
"#idp41589968">Recovery</a></span></dt>
|
||||
</dl>
|
||||
</dd>
|
||||
|
||||
@@ -997,8 +997,8 @@ alink="#0000FF">
|
||||
<div class="titlepage">
|
||||
<div>
|
||||
<div>
|
||||
<h3 class="title"><a name="idp46788704" id=
|
||||
"idp46788704"></a>2.1.3. Document types</h3>
|
||||
<h3 class="title"><a name="idp41562832" id=
|
||||
"idp41562832"></a>2.1.3. Document types</h3>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1091,8 +1091,8 @@ indexedmimetypes = application/pdf
|
||||
<div class="titlepage">
|
||||
<div>
|
||||
<div>
|
||||
<h3 class="title"><a name="idp46808384" id=
|
||||
"idp46808384"></a>2.1.4. Indexing
|
||||
<h3 class="title"><a name="idp41582512" id=
|
||||
"idp41582512"></a>2.1.4. Indexing
|
||||
failures</h3>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1132,8 +1132,8 @@ indexedmimetypes = application/pdf
|
||||
<div class="titlepage">
|
||||
<div>
|
||||
<div>
|
||||
<h3 class="title"><a name="idp46815840" id=
|
||||
"idp46815840"></a>2.1.5. Recovery</h3>
|
||||
<h3 class="title"><a name="idp41589968" id=
|
||||
"idp41589968"></a>2.1.5. Recovery</h3>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -6571,9 +6571,8 @@ for doc in results:
|
||||
|
||||
<div class="variablelist">
|
||||
<dl class="variablelist">
|
||||
<dt><a name="RCL.PROGRAM.PYTHONAPI.ELEMENTS.UDI" id=
|
||||
"RCL.PROGRAM.PYTHONAPI.ELEMENTS.UDI"></a><span class=
|
||||
"term">ipath</span></dt>
|
||||
<dt><a name="RCL.PROGRAM.PYTHONAPI.ELEMENTS.IPATH"
|
||||
id="RCL.PROGRAM.PYTHONAPI.ELEMENTS.IPATH"></a><span class="term">ipath</span></dt>
|
||||
|
||||
<dd>
|
||||
<p>This data value (set as a field in the Doc
|
||||
@@ -8652,10 +8651,10 @@ thesame = "some string with spaces"
|
||||
email user agents like Thunderbird usually store
|
||||
messages in hidden directories, and you probably
|
||||
want this indexed. One possible solution is to have
|
||||
'.*' in 'skippedNames', and add things like
|
||||
'~/.thunderbird' '~/.evolution' to 'topdirs'. Not
|
||||
".*" in "skippedNames", and add things like
|
||||
"~/.thunderbird" "~/.evolution" to "topdirs". Not
|
||||
even the file names are indexed for patterns in
|
||||
this list, see the 'noContentSuffixes' variable for
|
||||
this list, see the "noContentSuffixes" variable for
|
||||
an alternative approach which indexes the file
|
||||
names. Can be redefined for any subtree.</p>
|
||||
</dd>
|
||||
@@ -9306,11 +9305,13 @@ thesame = "some string with spaces"
|
||||
modified or deleted: as memory usage depends on
|
||||
average document size, not only document count, the
|
||||
Xapian approach is is not very useful, and you
|
||||
should let Recoll manage the flushes. The default
|
||||
value of idxflushmb is 10 MB, and may be a bit low.
|
||||
If you are looking for maximum speed, you may want
|
||||
to experiment with values between 20 and 80. In my
|
||||
experience, values beyond 100 are always
|
||||
should let Recoll manage the flushes. The program
|
||||
compiled value is 0. The configured default value
|
||||
(from this file) is 10 MB, and will be too low in
|
||||
many cases (it is chosen to conserve memory). If
|
||||
you are looking for maximum speed, you may want to
|
||||
experiment with values between 20 and 200. In my
|
||||
experience, values beyond this are always
|
||||
counterproductive. If you find otherwise, please
|
||||
drop me a note.</p>
|
||||
</dd>
|
||||
|
||||
@@ -4489,7 +4489,7 @@ for doc in results:
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry id="RCL.PROGRAM.PYTHONAPI.ELEMENTS.UDI">>
|
||||
<varlistentry id="RCL.PROGRAM.PYTHONAPI.ELEMENTS.IPATH">>
|
||||
<term>ipath</term>
|
||||
|
||||
<listitem><para>This data value (set as a field in the Doc
|
||||
|
||||
Reference in New Issue
Block a user