[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 17:19:14 PST 2011


--- Comment #5 from Marek Olšák <maraeo at gmail.com> 2011-03-01 17:19:14 PST ---
(In reply to comment #4)
> (In reply to comment #3)
> > There will be more performance improvements soon. I know how to improve it by
> > 50% or more, it's just not very high on my priority list currently.
> Oh!  Well, thank you for that (in advance)!
> My purpose in testing for regressions was to find a way to contribute back to
> the community.  Since I am not (yet) able to write code, or properly debug
> code, I thought I could at least report changes in performance and/or behavior
> in the build systems.  I'm getting the vibe that reporting performance
> regressions is not deemed a meaningful way to contribute.  Is that correct?

It's very useful to report performance regressions. Just in this case, it's not
obvious to me what's wrong with the commit. There are not many developers, so
it might be hard to get attention quickly especially if it's not a
show-stopper, but developers usually read bug reports and, thanks to that, are
aware of existing issues.

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