One more to add to this thread. I've been running a clean Gutsy install on my core2 duo machine. Tracker 0.6.6 came pre-installed, and I noticed that several minutes after startup (and I think sometimes after enough idle time) trackerd begins maxing out one of the cores. If I leave it alone for long enough, 5 minutes or so, it eventually calms down, but it is a bit distressing to see (and on my previous single-core system, it would cause a complete lock-up). I tried looking into configuration options and configured trackerd as in the attached file. basically, I tried to throttle back every aspect of the indexer as far as possible.
The new configuration seemed to have no noticeable effect on trackerd's habits, nor does the "Pause All Indexing" option in the system tray dropdown menu (it appears as though the setting takes effect only after the period of heavy cpu load ends). Memory usage appears contained at only 12 MB or so. My cache directory looks commensurate to cuby's in terms of file sizes. Tracker seems like a very useful app, and I'd love to use it, but sometimes I feel compelled to kill it, and therefore I can't rely on its indexes being up to date. Cheers, Matt ** Attachment added: "tracker.cfg" http://launchpadlibrarian.net/20869673/tracker.cfg -- trackerd always use 100% CPU https://bugs.launchpad.net/bugs/153319 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
