Merge lp:~compiz-team/compiz-bench-plugin/compiz-bench-plugin.fix_898548 into lp:compiz-bench-plugin
Status: | Merged |
---|---|
Merged at revision: | 42 |
Proposed branch: | lp:~compiz-team/compiz-bench-plugin/compiz-bench-plugin.fix_898548 |
Merge into: | lp:compiz-bench-plugin |
Diff against target: |
491 lines (+171/-120) 2 files modified
src/bench.cpp (+147/-114) src/bench.h (+24/-6) |
To merge this branch: | bzr merge lp:~compiz-team/compiz-bench-plugin/compiz-bench-plugin.fix_898548 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Daniel van Vugt | Approve | ||
Sam Spilsbury | Approve | ||
Review via email: mp+84433@code.launchpad.net |
Description of the change
Redesigned Benchmark so that it doesn't affect its own results (LP: #898548)
Benchmark contained several design flaws that made it inaccurate, including:
* A positive feedback loop meant the frame rate got stuck at maximum while benchmark was visible.
* While stuck at maximum frame rate it was constantly damaging the entire screen instead of just its own region, which made the desktop noticeably laggy.
* The method for smoothing used infinite decay, so was affected by its previous values from a long time ago. The new smoothing method is only affected by the past 2 seconds, for up-to-date accuracy.
* The frame rate reported and rate of smoothing depended on how often the benchmark was redrawn. The new code ensures that the measured frame rate is not affected by how often it is reported on screen.
* Colour: The old code represented a low frame rate as red (bad) and high as green. Actually, a low frame rate is normal on an idle desktop and good. So the colour has been reversed; low=green, high=red.
Re-proposal of https:/
Still looks good :)