I've been experiencing a performance regression when I'm using bochs, and using the latest git X and radeon. Browsing through boch's gui source, it looks like it's using a lot of bitmaps. I'm getting probably 1-2fps. What can I do to help narrow down what's causing this? xserver-xorg-video-radeon: Installed: 1:7.2.0+git1401090730.3213df~gd~s linux-image-3.13.0-999-generic: Installed: 3.13.0-999.201401020405
What versions of the components were you using when the performance was better? What hardware are you using? Please attach your xorg log and dmesg output from both the well performing setup and the poorly performing setup.
Created attachment 92012 [details] dmesg slow
Created attachment 92013 [details] Xorg log slow
I've tried different builds of the kernel, mesa, and the radeon driver from over the past three weeks, and always get the performance issues. I think when I remember there not being an issue must have been when I was using fglrx. So, there's not really a "regression" per se, but there is a performance issue somewhere. I forgot to mention in my first post, I'm using a duel card setup: Radeon R7 260x and a Radeon HD 4850.
You might try the glamor patches in bug 64738, bug 68524, bug 71813.
Well, bug 64738 and bug 71813 didn't help, and in fact gtkperf shows they made things worse. As for bug 68524, the current patch is still too slow to tell if it helps at all.
If the slowness is really related to bitmaps as you suggest, current glamor Git or the pending patches for glamor in the xserver tree might help.
With current xf86-video-ati Git master, does Option "ShadowPrimary" help? (I recommend enabling Option "TearFree" as well)
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/90.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.