Benchmark plugin severely affects its own results, making it inaccurate.

[Daniel van Vugt]

I noticed this when testing the fix for bug 880707. Without the benchmark plugin and just adding some debug logging to composite, I found with an idle desktop that composite (correctly) clocks down to only 2-5 FPS, and even zero when all screen activity stops. However running the Benchmark plugin, Benchmark always reports 60 FPS no matter what I do.

Similarly, my desktop is quick and responsive normally. But as soon as I press the Benchmark key combo to make it appear, my desktop becomes very laggy.

Clearly Benchmark is having a severe impact on the performance that it's meant to measure. And thus, the number it reports is going to be quite inaccurate.

[Daniel van Vugt (vanvugt)]

Fix committed to lp:compiz-bench-plugin r42.

[Daniel van Vugt (vanvugt)]

Fix committed to lp:compiz-plugins-extra revision 6.

[Launchpad Janitor (janitor)]

This bug was fixed in the package compiz-plugins-extra - 0.9.7.0~bzr9-0ubuntu1

---------------
compiz-plugins-extra (0.9.7.0~bzr9-0ubuntu1) precise; urgency=low

  * New upstream snapshot
    - Benchmark plugin severely affects its own results, making it
      inaccurate. (LP: #898548)
    - Plugins fail to build due to missing (renamed) TIMEVALDIFF (LP: #915236)
    - Some plugins no longer build due to undefined DEG2RAD (LP: #918554)
    - Merge (overwrite?) lp:compiz-*-plugin back into
      lp:compiz-plugins-{main,extra} (LP: #923572)
  * debian/control:
    - build-dep on latest compiz-dev and compiz-plugins-main-dev for
      ABI break
  * debian/rules:
    - pick the new abiversion file
 -- Didier Roche <email address hidden> Mon, 13 Feb 2012 15:31:20 +0100