Comment 54 for bug 64326

Paul, answers to your questions. :)

(1) It's worth noting that the initial crawl happens whenever the beagle daemon is started, not just when there is no index. But what I'm saying is that Beagle already never does that crawl on battery power if you have the config setting set. This feature was added in 0.2.8.

(2) If we can't check a few known files like /proc/acpi/ac_adapter, beagle assumes you're on AC power. (Because the altnerative is to assume you're always on battery, which isn't the right thing either.)

(3) The main issue I have with this is that there isn't any real user feedback. Most users aren't monitoring their CPU usage, so I'm not sure "boiling over" analogy works very well here. Short bursts of CPU usage are normal, but if the system feels unresponsive then we need to do some fine tuning to our scheduler. Pushing that decision off to the user feels like the wrong thing to me.