poor battery performance in Unity
Bug #599425 reported by
Jonathan Jesse
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Critical
|
Neil J. Patel | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The battery life on my Netbook is being eaten up by the new update. I think the problem is the index is being built on battery and decreasing the time I have on battery.
Updated on power, had a full charge, unplugged to go watch TV and logged into new Unity. Within 10 minutes I was at 1/2 battery life and 10 minutes later was done to 3/4 battery. Seems like an index was being built for the first time you use the search (zeitigest I think the application is called). Would be nice if there was a way to configure indexing on battery life.
RUnning a Dell Mini 9 w/ 10.04 completly up to date. 1 GB of RAM on my netbook
Related branches
Changed in unity: | |
milestone: | 2010-07-01 → 2010-07-08 |
Changed in unity: | |
milestone: | 2010-07-08 → 2010-07-15 |
Changed in unity: | |
milestone: | 2010-07-15 → 2010-07-22 |
Changed in unity: | |
importance: | High → Critical |
status: | Incomplete → In Progress |
Changed in unity: | |
milestone: | 2010-07-22 → 2010-07-29 |
Changed in unity: | |
milestone: | 2010-07-29 → 2010-08-05 |
Changed in unity: | |
milestone: | 2010-08-05 → 2010-08-19 |
Changed in unity: | |
status: | Fix Committed → Fix Released |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
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.