Crawling is not CPU bound, but I/O bound. You should not have a lot of CPU utilization. You can configure Tracker to select which top level folders to crawl. On Fri, 2017-06-16 at 09:03 +0100, Björn Johansson wrote:
Hi and thanks for the answer. So tracker goes through *all* files at
each startup?
Seems excessive to me and I have the file system watch turned on and
all changes should be
added on the fly. I could live with this if it was possible to
throttle back this indexing in the beginning, but regardless of
settings, it hogs 100% of one of four kernels and the hot air exhaust
is really uncomfortable.
cheers,
Bjorn
On Thu, Jun 15, 2017 at 2:13 PM, Jose Arroyo
<jose m arroyo se gmail com> wrote:
Hello Björn,
AFAIK, this is how tracker works:
The 1% thing stays there because during the initial crawling
phase, there's no way to accurately tell how much there is
left to recursively crawl in the root indexed directory. That
value is hard-coded and doesn't really mean much up until the
initial crawling is done.
On start-up, Tracker will recursively crawl the folders it is
configured to index. During this phase it will pick up every
single file and directory that isn't explicitly being ignored
via config options. For each file, it will compare the file's
last modified time on disk and the value in Tracker's DB to
decide if it needs to be updated or added or whatever. During
this phase Tracker will also set up monitors to keep track of
any modifications to any directories or files. This is done
every time the Tracker Miner File System is started.
So, that is what is happening behind the curtains while you
get these logs:
14 jun 2017, 06:55:10: 1% File System - Crawling
recursively directory 'file:///home/bjorn'
If this is taking an extremely long time, it is most likely
due to the sheer number of files and stuff present inside
'file:///home/bjorn'.
You may want to take a closer look at your configuration to
know what is being set up for recursive indexation and what
is being ignored. You could try adding some directories to the
ignore list if there is stuff that doesn't really need to be
indexed and could be taking a long time to crawl.
You can find some Tracker configuration options here:
https://wiki.gnome.org/Projects/Tracker/Documentation/Configuration
Hope this helps,
José
On 14 June 2017 at 08:03, Björn Johansson
<bjorn_johansson bio uminho pt> wrote:
Hi, I installed tracker a couple of weeks ago and
after some initial
struggle, it seemed to work. Tracker had a lot of work
doing the initial indexing,
but after that tracker indexes on the fly (I have
tested this and it seems to be working).
But now tracker seems to randomly begin to index the
file system although I believe that the initial index
finished. It also seem stuck on 1%:
bjorn@bjorn-ThinkPad-T450s:~$ tracker daemon
Store:
14 jun 2017, 06:46:01: ✓ Store -
Idle
Miners:
14 jun 2017, 06:46:01: ✓ Userguides -
Idle
14 jun 2017, 06:46:01: 1% File System -
Crawling recursively directory 'file:///home/bjorn'
14 jun 2017, 06:46:01: ✓ Applications -
Idle
14 jun 2017, 06:46:01: ✓ Extractor -
Idle
bjorn@bjorn-ThinkPad-T450s:~$ tracker daemon -w
Now listening for resource updates to the database
All nie:plainTextContent properties are omitted
Press Ctrl+C to stop
bjorn@bjorn-ThinkPad-T450s:~$ tracker daemon -f
Store:
14 jun 2017, 06:55:10: ✓ Store -
Idle
Miners:
14 jun 2017, 06:55:10: ✓ Userguides -
Idle
14 jun 2017, 06:55:10: 1% File System -
Crawling recursively directory 'file:///home/bjorn'
14 jun 2017, 06:55:10: ✓ Applications -
Idle
14 jun 2017, 06:55:10: ✓ Extractor -
Idle
Press Ctrl+C to stop
^Z
[2]+ Stopped tracker daemon -f
bjorn@bjorn-ThinkPad-T450s:~$ tracker daemon
--list-miners-running
Found 4 miners running:
org.freedesktop.Tracker1.Miner.Extract
org.freedesktop.Tracker1.Miner.Applications
org.freedesktop.Tracker1.Miner.Files
org.freedesktop.Tracker1.Miner.Userguides
bjorn@bjorn-ThinkPad-T450s:~$
tracker daemon -f or tracker daemon -w does not put
out any changes, although there seems to be miners
running.
tracker daemon -t and then -s stops and starts the
mining.
Is there a way to know if tracker is really doing
anything or it just hanged?
Is there a log file somewhere ?
thanks,
Björn
--
______O_________oO________oO______o_______oO__
Björn Johansson
Assistant Professor
Departament of Biology
University of Minho
Campus de Gualtar
4710-057 Braga
PORTUGAL
https://metabolicengineeringgroupcbma.github.io
www.bio.uminho.pt
Office direct +351-253 601517 | PT mob. +351-967 147
704 | SWE mob. +46 72 740 60 20
Dept of Biology (secretary) +351-253 60 4310 | fax
+351-253 678980
_______________________________________________
tracker-list mailing list
tracker-list gnome org
https://mail.gnome.org/mailman/listinfo/tracker-list
--
______O_________oO________oO______o_______oO__
Björn Johansson
Assistant Professor
Departament of Biology
University of Minho
Campus de Gualtar
4710-057 Braga
PORTUGAL
https://metabolicengineeringgroupcbma.github.io
www.bio.uminho.pt
Office direct +351-253 601517 | PT mob. +351-967 147 704 | SWE mob.
+46 72 740 60 20
Dept of Biology (secretary) +351-253 60 4310 | fax +351-253 678980
_______________________________________________
tracker-list mailing list
tracker-list gnome org
https://mail.gnome.org/mailman/listinfo/tracker-list
Attachment:
signature.asc
Description: This is a digitally signed message part