Hi, thanks for reporting the bug. I had a couple of questions:
1. Does the performance issue still occur when you log into Unity?
2. Did you run top at the time? What were the processes with the highest cpu usage if so?
3. Can you mv ~/.local/share/zeitgest ~/.local/share/zeitgeist.backup and then re-login and see if you get the same issues (as zeitgeist will rebuild it's index).
We don't do any content-level indexing, only index the filenames and paths of what's in your recently-used cache, I wouldn't expect zeitgiest to eat CPU like this, so definitley something is going wrong. I''ll mark as incomplete pending the information.
Hi, thanks for reporting the bug. I had a couple of questions:
1. Does the performance issue still occur when you log into Unity? share/zeitgest ~/.local/ share/zeitgeist .backup and then re-login and see if you get the same issues (as zeitgeist will rebuild it's index).
2. Did you run top at the time? What were the processes with the highest cpu usage if so?
3. Can you mv ~/.local/
We don't do any content-level indexing, only index the filenames and paths of what's in your recently-used cache, I wouldn't expect zeitgiest to eat CPU like this, so definitley something is going wrong. I''ll mark as incomplete pending the information.