[Bug 34493] r600g performance regression introduced by 467023e8 ( Marek Olšák : r600g: use the same upload buffer for vertices, indices, and constants)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 1 15:12:15 PST 2011


--- Comment #2 from Dave Witbrodt <dawitbro at sbcglobal.net> 2011-03-01 15:12:14 PST ---
(In reply to comment #1)
> It's unclear to me how using one buffer instead of three can decrease
> performance.

I am not a developer, so I cannot comment on the code.  Indeed, regarding the
other bug report I mentioned (#34156) I was asked by Henri (private msg) to do
some profiling tests:  I know what that means, but I do not (yet) have any
experience with it, and have not found time to experiment with it in the past 2
weeks.  I just barely know enough 'git' usage to create a local branch with the
(five) problem commits reverted.

I wonder if anyone else can confirm the regression(s) I am reporting.  I'm
using Mesa r600g on Radeon HD 5750.  Running performance tests at 3b1c1f02 (the
commit before performance dropped for me) followed by 467023e8 (the subject of
the current bug report) should reveal a big difference.

If not, then it's just me... and the bug could be rejected as invalid.  It
could be hardware-specific, it could be PEBKAC (if I did something wrong
creating the local branch with the 5 commits removed), etc.

I was planning on testing the Mesa HEAD this weekend, including updating my
local branch to see if any new commits are affecting performance.  Maybe these
code changes are features, not bugs -- providing other benefits more important
than the performance effects.  I was just so happy to see the major increase in
performance in January that I hate the idea of losing it in the more recent

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the dri-devel mailing list