From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36596] Major 2D performance bottleneck (most noticeable with compiz)
Date: Fri, 29 Apr 2011 02:06:54 -0700 (PDT) [thread overview]
Message-ID: <20110429090654.B5E4D13000C@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36596-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36596
--- Comment #6 from Michel Dänzer <michel@daenzer.net> 2011-04-29 02:06:53 PDT ---
(In reply to comment #4)
> The slowness coincides with very low CPU usage.
If sync to vblank is enabled in the compiz configuration, does disabling that
help? If not, does
Option "EnablePageFlip" "off"
and/or
Option "SwapbuffersWait" "off"
in xorg.conf help? (Verify in Xorg.0.log that the options are taking effect)
> Would it be useful to profile something anyway?
sysprof or oprofile won't be useful. If none of the above helps, it might be
possible to find out where compiz is blocking with something like perf, but I
don't know how offhand.
> BTW, I should have mentioned that I have to boot with the "noirqdebug" kernel
> parameter, otherwise the kernel will sometimes disable the Radeon's IRQ saying
> "irq 19: nobody cared" (the exact message is no longer in the logs). Once the
> IRQ was disabled, everything still worked, but more slowly.
Hmm, the radeon IRQ not working reliably might explain at least some of your
symptoms. FWIW, can you also attach the dmesg output, at least the lines
related to agp/drm/radeon?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-04-29 9:06 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 [this message]
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
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=20110429090654.B5E4D13000C@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).