You are not logged in.
I recently upgraded to gnome 3.12 and now when my computer boots up from being off, after about 15 minutes it runs really slowly because tracker-store and tracker-extract are taking all of my cpu time. I hadn't changed anything related to tracker since having gnome 3.10, but this didn't happen until after the upgrade. I saw this thread https://bbs.archlinux.org/viewtopic.php?id=129728, but the "solution" is to remove tracker. I don't want to do that. I just want to know if there's a way to reduce the clock-hogging. I changed the "Index content in background:" to "Only when computer is not being used" but I still end up having to pkill tracker-store in order to use the computer.
Last edited by MisterEwok (2014-04-26 13:49:13)
Offline
Had a similar issu here: https://bbs.archlinux.org/viewtopic.php?id=180249
Tracker can be controlled from the command line with tracker-control. What I did was try and narrow down what files were causing tracker-extract to freak out. Start by disabling all locations in Search and Indexing and turning on one at a time until one location causes it to break. You can then set the log verbosity of tracker to debug to get lots of output. Delete your indexed data and run
$ sudo journalctl -f in one terminal and
$ tracker-control -s
$ tracker-control -F in another terminal while monitoring your CPU load with htop or some other tool. Huge pain in the ass.
Offline
Thanks for the tips. I ended up just doing a tracker-control -rc (remove config and database, hard reset) and then tracker-control -s with tracker-control -F in another terminal and htop in yet another. I just let it do its thing. Extractor got to 93 percent before all of my memory AND SWAP were consumed and it quit. I then did a soft reset (tracker-control -e) and started it again. It took another few minutes and finished. Since then, when I start up my computer, it just does a quick check and finishes shortly. So apparently it just needed to redo its initial data population (I have no idea what I'm talking about), and now it's no longer a problem, even with its default settings for everything.
Offline