Comment 18 for bug 718427
Revision history for this message
| Jean-Francois Dockes (jean-francois-dockes) wrote | #18 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> By the way, how can I reduce the number of threads of the recollindex?
Short answer: adjust thrTcounts in config file.
See http://
or the comments in the default recoll.conf in /usr/share/
About preventing caching for files read by indexing, this can't be fully controlled because a large part of the data is not read by recollindex but by the helper applications.
For files read by recollindex itself, there was an attempt to prevent caching, based on an O_STREAMING flag which does not seem to be implemented on any current system. I guess that fadvise() could now be used instead.
In steady state, little indexing should take place, so a file would have to be really huge to have a significant effect on the page cache. I guess that a really big mbox file could fall in this case though.
What would be really useful would be if someone could correlate recoll activity with the system perturbation. At level 4, most relevant information will be printed to the log file. I'd gladly do it, except that I can't seem to be able to reproduce the issue.