On Monday 08 November 2010, Dale wrote:
> Robin Atwood wrote:
> > On Saturday 06 November 2010, Dale wrote:
> >> Dale wrote:
> >>
> >>
> >> This is getting weird. I haven't rebooted in a few weeks now. I tried
> >> to watch a video a bit ago and it was slow again. It was down to about
> >> 2 or 3 frames per second. It is awful. If I go tell it to switch to
> >> opengl, it gets fast again but after a while it will go back to being
> >> really slow. Why do I have to keep telling it to use nvidia's opengl
> >> when it says it is using it and I have switched to a few times? If it
> >> is using it, why does it slow down until I tell it to switch?
> >>
> >> I did do a huge KDE upgrade the other day. I don't recall seeing
> >> anything else X related being updated but I could have missed something
> >> in that LONG list. I did do a baselayout upgrade and portage itself has
> >> been upgraded a few times.
> >>
> >> Any ideas on why this thing keeps doing this? Would a reboot even help
> >> in this situation?
> >
> > When it gets very slow start up top and see what's using the CPU. My bet
> > is the Xserver. I have a GeForce 9400 GT 512MB and the xserver will
> > happily use 90% while nothing much is happening. Start a KDE4 app which
> > constantly updates (ktorrent, kps are good 3rd party examples) and the
> > xserver goes crazy.
> >
> > HTH
> > -Robin
>
> Nope, it wasn't that here. This is what top says:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 17995 root 20 0 45360 15m 3360 R 89.6 0.7 0:35.72 glxgears
> 32113 dale 20 0 305m 162m 27m S 3.3 8.0 17:56.38 seamonkey-bin
> 31796 root 20 0 187m 76m 30m S 2.0 3.8 21:51.94 X
> 31914 dale 20 0 286m 47m 24m S 1.7 2.3 18:04.02 kwin
>
> It was glxgears that was taking up the most CPU time but I think the
> rest of it was processing the video. Thing is, nothing has been updated
> and I have not even logged out of KDE since it was working this
> morning. So, without me doing a single thing, it has stopped working as
> it should. It's like the card is being bypassed as far as it using its
> own CPU to process the picture.
>
> Oh, look at this miserable mess:
>
> 2 frames in 8.5 seconds = 0.236 FPS
> 2 frames in 8.7 seconds = 0.230 FPS
> 2 frames in 8.3 seconds = 0.241 FPS
> 2 frames in 8.1 seconds = 0.246 FPS
> 2 frames in 8.1 seconds = 0.247 FPS
> 2 frames in 8.1 seconds = 0.247 FPS
> 2 frames in 8.3 seconds = 0.241 FPS
>
> Trust me, to see those little wheels turn that slow is really boring.
>
> Going back to single user and switch this again. I have noticed that
> telling it to switch to nvidia's opengl while in single user mode does
> seem to last longer. Going to re-emerge the drivers to while I am at
> it. Can't hurt anything.
>
> Still open to ideas cause this is weird.
AFAIK, all "eselect opengl" does is set up some symlinks so you use NVidia
libraries and not Mesa ones. You might want to poke around and check last
access dates.
HTH
-Robin
--
----------------------------------------------------------------------
Robin Atwood.
"Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------
