From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36596] New: Major 2D performance bottleneck (most noticeable with compiz)
Date: Mon, 25 Apr 2011 17:18:25 -0700 (PDT) [thread overview]
Message-ID: <bug-36596-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36596
Summary: Major 2D performance bottleneck (most noticeable with
compiz)
Product: Mesa
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: bluesloth600@gmail.com
Created an attachment (id=46072)
--> (https://bugs.freedesktop.org/attachment.cgi?id=46072)
lspci -v
With compiz, making a new window or resizing a window makes the framerate drop
to 2 fps for about 5 or 6 seconds.
Running conky makes the frame rate that low most of the time, alternating with
brief moments of decent performance. With a more traditional window manager
(openbox), a lot of programs (including xterm) freeze briefly every time conky
redraws itself, so it seems like that particular problem is not entirely a Mesa
bug. Things run smoothly with the fbdev Xorg driver.
I tried compiz with the --no-fbo option once, and the framerate stayed at 2 fps
until I rebooted. Restarting X didn't help, I actually had to reboot.
With the classic Mesa drivers, compiz would sometimes take a long time to
render a few frames, but not nearly as often as it does now.
I've had this problem with the Debian Mesa packages since they switched to
gallium, and with git master (as of yesterday) built with and without
--enable-gallium-llvm.
I run Debian sid on a Dell Inspiron 1721 with an integrated Radeon X1270.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-26 0:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:18 bugzilla-daemon [this message]
2011-04-26 0:24 ` [Bug 36596] Major 2D performance bottleneck (most noticeable with compiz) 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
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=bug-36596-502@http.bugs.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).