dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27069] OpenGl is slower on dri2
Date: Thu,  1 Sep 2011 16:20:13 -0700 (PDT)	[thread overview]
Message-ID: <20110901232013.4C18E1300BF@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27069-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=27069

--- Comment #3 from Stefan Dösinger <stefandoesinger@gmx.at> 2011-09-01 16:20:12 PDT ---
This problem still exists, UMS(as far as 3D is still working with it) is much
faster than KMS. Unfortunately the only app that's still working with UMS in
Mesa 7.11 is glxgears.

On my r250 GPU glxgeares runs at 2600 fps with UMS, 1070 with KMS(default
Window size). At 1400x1050 the numbers are 370 fps(UMS) and 60 fps(KMS).

I don't think vsync causes the issue, disabling it seems to work fine, at least
for windowed apps.

etracer is still a lot slower with KMS than it used to be. At 1400x1050 and
otherwise default settings it runs at 15-20 fps. With an ancient Mesa version I
tested today(6.4.2) it runs at a pretty okish 60 fps at the same settings.

The problem seems to be on the GPU side. Whenever the problem occurs the CPU is
idle and the GPU working, and increasing the rendering resolution makes the
problem worse. The unfortunate situation this creates is that the 6 years old
Mesa on my old hard drive vastly outperforms Mesa 7.11 in many rendering
situations.

I could not spot any CPU side problems, but the GPU slowness makes it hard to
test. My unscientific guess is that in setups where the KMS GPU slowness
doesn't matter Mesa 7.11 is about 50% faster than Mesa 6.4.2. (etracer with a
tiny resolution, long view range and lots of objects)

I'll test r300 on a Radeon X1600 GPU over the weekend. This GPU/driver combo is
pretty slow as well, but I'm not sure if r300 still supports UMS.

-- 
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

  parent reply	other threads:[~2011-09-01 23:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14 14:13 [Bug 27069] New: OpenGl is slower on dri2 bugzilla-daemon
2010-03-15 11:12 ` [Bug 27069] " bugzilla-daemon
2010-03-15 16:52 ` bugzilla-daemon
2011-09-01 23:20 ` bugzilla-daemon [this message]
2011-09-01 23:21 ` bugzilla-daemon
2011-09-02 12:17 ` bugzilla-daemon
2011-09-02 13:11 ` bugzilla-daemon
2011-09-02 13:20 ` bugzilla-daemon
2011-09-02 13:49 ` bugzilla-daemon
2011-09-03 18:45 ` bugzilla-daemon
2011-09-03 18:48 ` bugzilla-daemon
2011-09-03 18:50 ` bugzilla-daemon
2011-09-03 19:09 ` bugzilla-daemon
2011-09-06  1:57 ` bugzilla-daemon
2014-01-23 11: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=20110901232013.4C18E1300BF@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