Comment 36 for bug 64326

Joe: Thanks for the information.

As Joe says, there's several separate issues present in this report, that need to be separated out into separate individual reports.

(1) We should probably probably _untick_ the following setting by default:

  [ ] Index data while on battery pack.

What is particularly important is have the setting:

  [ ] Perform full index while on battery power.

This comes into use when the user first installs/upgrades Beagle and Beagle uses 100% CPU for an infinity amount of time doing the initial extra. (rm ~/.beagle/ if you want to repeat this!). By this time the user is annoyed enough with Beagle that they stop it; not realising that in the longer term Beagle might be a little saner.

(2) Joe: if Beagle detects a switch to ACPI power (how is it doing this, SIGPWR?), could we have beagle stop *immediately*. Having a feedback to the user is important so that they associate "remove AC power" with "stop of hard-disk activity".

Indexing of the interrupted file can easily be restarted later. If it was a particularly huge file that took 10minutes to index, I'd be wanting that battery power aswell!

(3) Joe: Could we have some level of self throttle (as opposed to just setting Nice) for Beagle. Running the CPU twice as fast uses eg. Four times the amount of electricity, produces more heat and the like. Perhaps Beagle could have a slider for how much CPU/Disk I/O is allowed and we have the default of having that slider quite low.