Tracker seems to be a resource hog...

[dd_wizard]

Just curious if others see this before I file a bug report. Occasionally, I see CPU resources pet. When it happens, tracker appears to be the culprit:

 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                            
1620 gene      20   0  566m  71m  33m D 47.8  3.6   8:04.64 tracker-store

and

 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                            
1509 gene      39  19  284m  28m  26m R 93.0  1.4   1:33.66 tracker-miner-fs

Any ideas about what is going on here?

Thanks,
dd_wizard

[AdamW]

it's a file indexing service. i fully expect to die without ever having seen one of those which _doesn't_ have a resource pegging bug of some kind or another.

certainly file it, but track down some logs first, tracker should log somewhere: the devs will need to know exactly what it's choking on to fix the problem. with the aid of the logs you may be able to isolate it to some particular file or type of file, then attach it to the bug.

[dd_wizard]

OK, will do. I'll have to turn it back on though. After doing some reading, it didn't look that useful for me. So, I turned all three tracker daemons off in gnome-session-properties. Oddly enough, that took care of the resource problem.

dd_wizard

[AdamW]

well, tracker will be the foundation of all the new GNOME 3 features for finding files, so it's going to be pretty important to 'intended' use of GNOME 3. AIUI anyway.

[dd_wizard]

Bug 734921 submitted.

dd_wizard