Re: [opensuse] Beagle eats my CPU
Debajyoti Bera wrote:
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.
50GB is a lot ... it would definitely take some days to completely index it.
This is MONTHS after setting up the system. And the /home was copied over from another machine shortly after this one was set up and running -- beagled had settled down many weeks earlier before this incident.
Indexing takes CPU but the point is when you need it, beagle will slow down automatically.
That's the claim. However, I'm still experiencing great discrepencies between the advertised behavior and what actually happens on my systems.
I suspect that is what you are seeing ... i.e. nothing unexpected. You might not like the default but lets first confirm that there is no bug. Would you mind sending me a few things ?
1) Output of "tail -n 100 ~/.beagle/Log/current-Beagle" (should not contain any personal information)
2) Output of "tail -n 100 ~/.beagle/Log/current-IndexHelper"
3) Output of "ls -l ~/.beagle/Log"
(If you have stopped beagle, which I fear you did, then skip the rest and send me the output of "beagle-manage-index ~/.beagle/Indexes/FileSystemIndex/ info").
4) Output of "beagle-info --index-info"
5) Output of "beagle-info --status"
6) On a terminal do, tail -f ~/.beagle/current-Beagle Then $ kill -USR1 `pidof beagled` $ kill -USR2 `pidof beagled` Send me the output of the lines printed on the output.
Also, do you have any p2p downloading going on and its temporary folder under beagle's watch ?
No. As I said..the system was essentially IDLE for over 3 days. The only filesystem activity would be receipt of e-mail and logging in /var/log.
Many many thanks, - dBera (Beagle developer)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
This is MONTHS after setting up the system.
And the /home was copied over from another machine shortly after this one was set up and running -- beagled had settled down many weeks earlier before this incident.
*sigh* Its a bug. A new one, all the earlier ones with the same symptom were fixed.
Recent example -- desktop machine at home. SuSE 10.3 on an AMD_64_x2. Filesystems spread across 4 SCSI
SuSE 10.3 had beagle-0.2.something and would have caused this. But you claimed that you have the latest (beagle 0.3.7 on mono-1.9) so I don't yet have a clue what could be causing this. Maybe the 64-bit is introducing some bug; can't say without some investigation. If you want, please file a bug and I can ensure it will get prompt attention. - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE / Mandriva / Inspiron-1100 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Debajyoti Bera wrote:
This is MONTHS after setting up the system.
And the /home was copied over from another machine shortly after this one was set up and running -- beagled had settled down many weeks earlier before this incident.
*sigh* Its a bug. A new one, all the earlier ones with the same symptom were fixed.
beagle seems to becoming the modern-day OS/360... Every bug fix introduces new ones.
Recent example -- desktop machine at home. SuSE 10.3 on an AMD_64_x2. Filesystems spread across 4 SCSI
SuSE 10.3 had beagle-0.2.something and would have caused this. But you claimed that you have the latest (beagle 0.3.7 on mono-1.9) so I don't yet have a clue what could be causing this. Maybe the 64-bit is introducing some bug; can't say without some investigation.
If you want, please file a bug and I can ensure it will get prompt attention.
- dBera
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Debajyoti Bera
-
Evens Garde