Re: [Rhythmbox-devel] Response and CPU problems

["Andrew Conkling" <andrew conkling gmail com>]

Hello again,

On 7/16/06, Jonathan Matthew <jonathan kaolin wh9 net> wrote:
> On Sun, Jul 16, 2006 at 09:46:51PM -0400, Andrew Conkling wrote:
> > Hello,
> > I'm using 0.9.4.1 on Ubuntu Dapper.  I've been having problems with
> > RB's speed and CPU usage during use.  I have about 80G of music
> > mounted over NFS on a computer on my LAN whence I play most of my
> > music.
> >
> > Frequently, I'll notice a 1-10 second delay in the UI (i.e. pressing a
> > key or highlighting a button takes 10 seconds to respond) and RB using
> > about 10% of my (1.8 GHz Pentium M) CPU.
>
> It sounds like this might be something to do with file monitoring.  You
> could try disabling file monitoring (the 'watch my library for new
> files' option in the library preferences) to see if that's the case.

I haven't forgotten about this, it just took me a while to reproduce
the problem.  I've even had file monitoring enabled.  There's nothing
different with my system than there has been, but it seems to be laggy
tonight.  So here goes.

> Getting some strace output might also be helpful.  If you could run
> 'strace -p `pidof rhythmbox` -o rb-strace' for a few seconds while this
> is happening and put the resulting file somewhere (please don't send it
> to the whole list) we'd be able to see what was going on.  Output from
> 'ls -l /proc/`pidof rhythmbox`/fd' might also be required to figure out
> what's happening.

Actually, strace didn't produce much:

# strace -p `pidof rhythmbox` -o rb-strace
Process 5937 attached - interrupt to quit
Process 5937 detached

And ls had a bit more, but still not much:

~ ls -l /proc/`pidof rhythmbox`/fd
total 30
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 0 -> /dev/null
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 1 -> /dev/null
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 10 -> socket:[28083]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 11 -> socket:[28087]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 12 -> socket:[28089]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 13 -> socket:[28092]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 14 -> socket:[28096]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 15 -> socket:[28093]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 16 -> socket:[28097]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 17 -> pipe:[28099]
l-wx------ 1 andrew andrew 64 2006-08-01 23:15 18 -> pipe:[28099]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 19 -> pipe:[28100]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 2 -> /dev/null
l-wx------ 1 andrew andrew 64 2006-08-01 23:15 20 -> pipe:[28100]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 21 -> pipe:[28101]
l-wx------ 1 andrew andrew 64 2006-08-01 23:15 22 -> pipe:[28101]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 23 -> socket:[28102]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 24 -> socket:[28105]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 25 -> socket:[28114]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 26 -> socket:[28141]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 27 -> inotify
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 28 -> socket:[30018]
lrwx------ 1 andrew andrew 64 2006-08-01 23:15 3 -> socket:[28078]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 32 -> pipe:[30011]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 4 -> pipe:[28080]
l-wx------ 1 andrew andrew 64 2006-08-01 23:15 5 -> pipe:[28080]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 6 -> pipe:[28081]
l-wx------ 1 andrew andrew 64 2006-08-01 23:15 7 -> pipe:[28081]
lr-x------ 1 andrew andrew 64 2006-08-01 23:15 8 -> pipe:[28082]
l-wx------ 1 andrew andrew 64 2006-08-01 23:15 9 -> pipe:[28082]

Any more info you could provide on this would be very helpful; it's
rather tedious when it happens.  (Restarting doesn't help.)

Thanks very much,
Andrew Conkling