https://bugzilla.novell.com/show_bug.cgi?id=356971 User dbera.web@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=356971#c3 --- Comment #3 from D Bera <dbera.web@gmail.com> 2008-07-06 06:23:16 MDT --- (In reply to comment #0 from Pavel Nemec)
I run abuild application to build and rpm and I realise that my system is very irresponsible. I run top to obtain information and I realise that beagled-helper spin constantly about 90% of cpu.
this is snip of top: top - 15:13:45 up 20 days, 23:38, 24 users, load average: 5.28, 3.76, 2.42 Tasks: 189 total, 4 running, 185 sleeping, 0 stopped, 0 zombie Cpu(s): 25.3%us, 3.5%sy, 47.8%ni, 0.0%id, 22.6%wa, 0.3%hi, 0.5%si, 0.0%st Mem: 2061376k total, 2052288k used, 9088k free, 133804k buffers Swap: 4225052k total, 207692k used, 4017360k free, 603600k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 19293 pavel 39 19 262m 35m 11m R 97 1.8 732:42.68 beagled-helper 12286 root 19 0 10232 8192 2048 R 52 0.4 0:05.08 rpm.bin
beagled-helper should watch "load" walue and respect it.
It actually does. I suspect this has something to do with rpm. Currently rpm files are indexed by parsing the output of "rpm -q --queryformat ..." so large rpms can be a bit costly. (The rpm process is automatically killed if it runs for too long). Or it was some file whose parser was causing the high load. Usually the file parsers are fixed if the problem can be detected. So if you spot such a file, please report and attach the file. Sending SIGUSR2 to beagled-helper will cause beagled-helper to print the name of the currently indexing file to ~/.beagle/Log/current-IndexHelper -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.