Created attachment 69265
Bisect log (Kayden)
I managed to reproduce this after all.
Steps to reproduce:
1. Enable KWin's "Show FPS" counter plugin.
2. Configure the "Present Windows" effect to one of the screen corners.
3. Mash that repeatedly and watch the FPS counter.
On HD 4000, a good version of Mesa results in perhaps ~55-60 FPS. Bad
Mesa can be as low as 17 FPS, often mid-30s.
I also went ahead and bisected it (the log is attached).
e943e5c291c5f4c017f9f5a483f1940313333fc3 is the first bad commit
commit e943e5c291c5f4c017f9f5a483f1940313333fc3
Author: Chad Versace <chad.vers...@linux.intel.com>
Date: Thu Aug 2 17:13:17 2012 -0700
intel: Advertise multisample DRI2 configs on gen >= 6
This turns on window system MSAA.
So in other words, it looks like KDE is using multisampling now, whereas
it didn't before. Our implementation of that may not be optimal, and
may have bugs, but it will always be far slower than single sampling.
My next question would be: how can one disable the use of MSAA in KWin
or Plasma? I don't see an option for that, but I would be really
surprised if there wasn't one...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1061073
Title:
Desktop effects are slow and desktop corruption using mesa 9
To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1061073/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
