https://bugs.freedesktop.org/show_bug.cgi?id=34493
--- Comment #6 from Dave Witbrodt dawitbro@sbcglobal.net 2011-03-01 20:01:16 PST --- (In reply to comment #5)
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.
OK, thanks for the clarification.
I will continue my local testing of Mesa master and my own branch with any problem commits I find reverted -- as long as I am able, I mean.
In the coming weeks I should finally be finding time to begin learning the code. Maybe this sort of testing -- profiling, identifying code changes that affect performance, and explaining the reason for those effects -- will be my way of learning the code base.
FTR, by pointing out performance problems I find, I am not seeking immediate fixes or attention for those particular problems. I am merely hoping to provide info to developers, in case the info is important. Mesa actually works fine for me from master... just 1/3 slower. ;)