From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36596] Major 2D performance bottleneck (most noticeable with compiz)
Date: Fri, 6 May 2011 23:29:03 -0700 (PDT) [thread overview]
Message-ID: <20110507062903.298A613004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36596-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36596
--- Comment #10 from Jason Cassell <bluesloth600@gmail.com> 2011-05-06 23:29:03 PDT ---
(In reply to comment #9)
> Really sounds like the GPU IRQ doesn't work (reliably). Do the numbers on the
> radeon line in /proc/interrupts still increase when the problem occurs?
Not a lot. When everything's working, moving wobbly windows involves hundreds
of interrupts. When it's at 2 fps, there are only a few, at most. Possibly
none.
> Maybe try some IRQ related kernel debugging options as applicable, to see if
> any of them works around the problem.
noapic didn't make any difference.
I can't make the "irq 19: nobody cared" problem happen any more. I don't
remember what kernel version I had last time it happened, but with 2.6.38.5 at
least, it's not happening for me anymore (so far). When it was happening,
irqpoll and irqfixup didn't help.
Debian sid just went through a lot of upgrades. I now have xserver 1.10.1 and
llvm 2.8. Yesterday I did a git pull and rebuilt Mesa again. The performance
problem's still there.
My hunch, based on my immense lack of knowledge of video drivers and GPUs, is
that when things slow down, it's because textures are being moved around in
memory. When I rotate the cube in compiz to go to another desktop, sometimes
it stutters a bit, as if the texture for the other desktop isn't in the GPU's
memory yet, or something. When I resize a window, the newly sized window is a
new texture, and something needs to be done with that new texture which
apparently takes 5 seconds and keeps the GPU too busy to do much else.
You probably shouldn't listen to me though, since I'm just guessing and I don't
really know how anything works.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-05-07 6:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:18 [Bug 36596] New: Major 2D performance bottleneck (most noticeable with compiz) bugzilla-daemon
2011-04-26 0:24 ` [Bug 36596] " bugzilla-daemon
2011-04-26 0:41 ` bugzilla-daemon
2011-04-26 0:43 ` bugzilla-daemon
2011-04-26 0:45 ` bugzilla-daemon
2011-04-26 0:45 ` bugzilla-daemon
2011-04-27 10:28 ` bugzilla-daemon
2011-04-28 23:36 ` bugzilla-daemon
2011-04-28 23:38 ` bugzilla-daemon
2011-04-29 9:06 ` bugzilla-daemon
2011-04-30 5:02 ` bugzilla-daemon
2011-04-30 5:03 ` bugzilla-daemon
2011-05-02 9:34 ` bugzilla-daemon
2011-05-07 6:29 ` bugzilla-daemon [this message]
2011-05-09 14:04 ` bugzilla-daemon
2011-06-06 4:40 ` bugzilla-daemon
2011-06-06 4:44 ` bugzilla-daemon
2013-01-09 11:55 ` bugzilla-daemon
2013-01-11 10:56 ` bugzilla-daemon
2019-09-18 18:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110507062903.298A613004F@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).