Debajyoti Bera wrote:
My impression is that it looks all of the time and never ever stops when an initial index has been built even when there have been no further changes.
That is definitely not the case, at least with the version on 11.0. I am pretty confident about that. After initial indexing is over, there should be no activity.
Unfortunately, it doesn't seem to be that way. Recent example -- desktop machine at home. SuSE 10.3 on an AMD_64_x2. Filesystems spread across 4 SCSI disks (2 GB /tmp on a 9 GB SCSI, and other filesystems on an 18 GB SCSI, and a few GB at the beginning logical block of two 36GB SCSIs, and then my /home and /local on a 150GB SATA (about 50 GB unused, and the /home holding about 50GB and /local mostly unused.) After a few days away from home, I come back to find beagle taking 30% CPU...this on a machine which was built several months ago, and doesn't currently have a lot of filesystem activity on it. I've found it running away merrily even after several days away from home on military training...consuming a significant percentage of CPU cycles on an AMD_64_x2. I'm close to the point of removing it again.
- dBera
PS: There was a corner case in the versions in 10.x and earlier which caused endless crawling like you said but that was fixed long ago.
The currently installed version is the same one that the beagle website claims to be the latest... so, it seems it still isn't fixed.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org