From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 50616] New: glClear occasionally taking >60ms
Date: Sat, 02 Jun 2012 13:29:45 +0000 [thread overview]
Message-ID: <bug-50616-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=50616
Bug #: 50616
Summary: glClear occasionally taking >60ms
Classification: Unclassified
Product: Mesa
Version: 8.0
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: curaga@operamail.com
I have a test app that draws 65k point sprites, apitrace:
http://kiwi6.com/file/0c0512r1no (980kb).
Apitrace says that on average glClear takes 28ms, and many clear calls take
over 60ms. Surely it shouldn't take that long?
If it were because of tearing prevention, it should take at most 16ms (1/60Hz).
--
vblank_mode=0 had no change, oprofile says Mesa takes less than 2% cpu.
Latencytop shows radeon_fence_wait taking between 3 and 5ms during rendering.
--
Mesa 8.0.3
Linux 3.2.17
HD4350 / r600g
--
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:[~2012-06-02 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 13:29 bugzilla-daemon [this message]
2012-06-02 13:32 ` [Bug 50616] glClear occasionally taking >60ms bugzilla-daemon
2012-06-03 15:08 ` bugzilla-daemon
2012-06-03 15:22 ` bugzilla-daemon
2012-06-05 10:46 ` bugzilla-daemon
2012-06-05 18:42 ` bugzilla-daemon
2012-06-06 9:13 ` bugzilla-daemon
2012-06-06 11:16 ` 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-50616-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.