From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69341] [radeonsi] KDE 4.11 is EXTREMELY slow with Raster QT backend
Date: Mon, 23 Sep 2013 20:03:49 +0000 [thread overview]
Message-ID: <bug-69341-502-PLJ73UYAH7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69341-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 759 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69341
--- Comment #8 from Denis M. (Phr33d0m) <god@politeia.in> ---
(In reply to comment #7)
> Yes that's the same corruption I have with the native backend. I suggest you
> to have a look at top: native isn't slow, but aftware a few minutes the X
> process starts eating the CPU ,that's the reason ;)
In my case, X doesn't normally use much cpu (~10-15%) (well, really depends on
your definition of 'much'), but there are moments (every 2-3 seconds) where it
peaks at ~45-60% which causes everything to lag for a moment (for example if I
move a window or even with glxgears)...
And btw, thanks for the vblank tip, it helped a little.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1633 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-09-23 20:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-69341-502@http.bugs.freedesktop.org/>
2013-09-15 12:27 ` [Bug 69341] [radeonsi] KDE 4.11 is EXTREMELY slow with Raster QT backend while X11/XRender has graphical glitches bugzilla-daemon
2013-09-15 12:33 ` bugzilla-daemon
2013-09-15 12:33 ` [Bug 69341] [radeonsi] KDE 4.11 is EXTREMELY slow with Raster QT backend bugzilla-daemon
2013-09-23 14:47 ` bugzilla-daemon
2013-09-23 15:10 ` bugzilla-daemon
2013-09-23 20:03 ` bugzilla-daemon [this message]
2013-09-23 20:14 ` bugzilla-daemon
2013-09-27 14:25 ` bugzilla-daemon
2013-10-02 19:47 ` bugzilla-daemon
2013-10-04 20:29 ` bugzilla-daemon
2013-10-09 10:19 ` bugzilla-daemon
2013-10-09 10:21 ` bugzilla-daemon
2013-10-09 16:58 ` bugzilla-daemon
2013-10-21 17:05 ` bugzilla-daemon
2013-10-21 17:09 ` bugzilla-daemon
2013-10-23 19:09 ` bugzilla-daemon
2013-10-24 21:30 ` bugzilla-daemon
2013-10-25 9:30 ` bugzilla-daemon
2013-10-27 12:52 ` bugzilla-daemon
2013-10-27 13:03 ` bugzilla-daemon
2013-10-27 14:09 ` bugzilla-daemon
2013-10-27 18:38 ` bugzilla-daemon
2013-10-27 21:00 ` bugzilla-daemon
2013-11-01 19:16 ` bugzilla-daemon
2013-11-01 23:06 ` bugzilla-daemon
2013-11-05 19:57 ` bugzilla-daemon
2013-11-05 22:00 ` bugzilla-daemon
2013-11-06 18:58 ` bugzilla-daemon
2013-11-07 13:13 ` bugzilla-daemon
2013-11-09 2:02 ` bugzilla-daemon
2013-11-16 16:30 ` bugzilla-daemon
2013-11-16 16:35 ` bugzilla-daemon
2013-11-16 16:35 ` bugzilla-daemon
2013-11-16 16:40 ` bugzilla-daemon
2013-11-16 20:04 ` bugzilla-daemon
2013-11-16 21:24 ` bugzilla-daemon
2013-11-16 23:41 ` bugzilla-daemon
2013-11-17 13:40 ` bugzilla-daemon
2014-01-10 12:09 ` bugzilla-daemon
2014-01-10 12:33 ` bugzilla-daemon
2015-01-28 7:37 ` bugzilla-daemon
2015-01-28 8:52 ` bugzilla-daemon
2015-01-28 8:54 ` 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-69341-502-PLJ73UYAH7@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).