Mailinglist Archive: opensuse-bugs (8107 mails)

< Previous Next >
[Bug 237770] beagled is doing too much work
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 12 Feb 2007 09:33:17 -0700 (MST)
  • Message-id: <20070212163317.5749225C887@xxxxxxxxxxxxxxxxxxxxxx>

------- Comment #8 from joeshaw@xxxxxxxxxx 2007-02-12 09:33 MST -------
Total CPU usage on screensaver is the intended behavior (assuming you're not on
laptop battery). The idea is that since you're away from your computer, Beagle
can index your data as quickly as possible without interfering with your usage
of the machine. We should probably make that an option, but that should be
filed as a separate enhancement request bug.

If the CPU usage extends beyond returning to the machine and turning the
screensaver off, that would be a bug. Since a number of these have been fixed
in the newer versions, I'd ask that you update first and see if you still see
the problem. There have also been substantial fixes to memory usage so the 163
megs RSS should decrease quite a bit (and presumably virtual as well, although
that's a harder number to analyze).

The default log level as shipped is low and won't give you any useful
information about CPU usage or what it's indexing. You can either send the
beagled process SIGUSR1 to bump it up, or restart beagled with the --debug
option (beagled --replace --debug). That will hopefully help things. Newer
versions also allow you to send SIGUSR2 to the beagled-helper process to report
what is presently being indexed and how long it's been running. That would
only be useful if it were the beagled-helper process that was pegging the CPU,
not beagled.

The only way to get useful information from the log files would be to run
beagled with the --debug option. You can send SIGUSR1 to the running beagled

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >