compiz is running at 60+ wakeups per second

[Francis Ginther]

According to one of the unity/manual-tests, compiz should run well under 50 wakeups per second while the UI is idle. It is currently running at 60+ wakeups per second. On prior builds, it run much lower (under 20).

Testing with:
compiz - 1:0.9.8.2+bzr3377-0ubuntu1~test2
nux - 3.6.0-0ubuntu1~test2
unity - 6.6.0-0ubuntu1~test1

[Test Case]
From unity/manual-tests/Launcher.txt

Launcher autoscroll wake-ups
----------------------------
This test makes sure that the timer controlling autoscroll animations does
not keep running (at 50Hz) when it's not required to animate anything. This
is LP: #917210.

Setup:
#. Ensure the screen is idle, with very little changing.
#. Open a terminal and start a tool that can measure process wakeups per
   second. You can choose one of:
     - gnome-power-statistics (click on Processor)
     - powertop
     - eventstat

Actions:
#. Hover the mouse pointer over the top end of the Launcher. That's just above
   the Ubuntu icon.
#. Hover the mouse pointer over the bottom end of the Launcher. That's over
   the bottom of the trash icon.
#. Move the mouse pointer back to the centre of the screen and leave it there.
#. Wait 30-60 seconds, leaving the screen idle before verifying the Outcome.

Expected Result:
  The number of wakeups per second (events per second) reported for the
  compiz process should be much lower than 50.

[Observed Result]
Compiz wakeups per second stayed above 60 the entire time.

[Bilal Akhtar (bilalakhtar)]

I didn't have this problem with Unity trunk; my wakeups stayed below 20.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1034055, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.