Comment 258 for bug 252094

How to Report an Intel Performance Problem

First, make a new bug. The easiest way, which will pull in a lot of useful logs and config files, is:

  ubuntu-bug -p xserver-xorg-video-intel

Second, select a very precise title for the bug. If you use a generic title like "performance sucks" it will just attract others with unrelated performance issues to comment on and hijack your bug, which just wastes everyone's time, most especially your own!

Next, provide very specific steps to reproduce the issue. Reproduce the problem yourself several times (including after a fresh reboot) so you're certain it's just not some random quirk. When a developer or tester is able to easily reproduce your issue, it makes it immensely easier for them to figure out how to fix it, and to be certain that your issue is gone.

For performance bugs, a few other bits of data can be useful, including `glxinfo` and `xdpyinfo` output, and a video or photo (particularly if the perf issue is accompanied by graphics corruption or glitches.) See http://intellinuxgraphics.org/how_to_report_bug.html as the official guide on what to include.

Finally, vary your setup and see how many different ways you can or can't reproduce it. Try it with compiz on vs. off, or on a different version of Ubuntu, or a different distro with the same xserver/driver version, or on another computer also running Ubuntu but with different Intel graphics chips. Or try out some xorg.conf driver parameters listed in `man intel` to see how they influence things.

If you follow these guidelines, you'll stand a much better chance of getting your performance issue looked at. Be aware, though, that with performance issues Intel is mainly concerned with what is in their git tree; they may ask you to build and test their latest code, and if the issue doesn't exist there they'll consider the problem solved.