Comment 17 for bug 599425

Mark, agreed, but 40% is too much for motion events (the launcher wasn't moving or unfolding, as it had already unfolded, this was caused by the hit-detection in Clutter).

So, we've been working together on this yesterday and today, and here's an update:

 - Motion event hit-detection in Clutter (using glReadPixels) is the cause of the mouse issues. Jason is working on a patch to simplify the hit detection. Hopefully this will work and visibly increase the performance of Clutter on netbooks

- Idle CPU usage. This is caused by Clutter not properly supporting sub-region updates, and Unity painting a lot of things. Gord is working on implementing a proof-of-concept idea to see if we can solve this in a clever way for Unity.

If we get some positive results, we hope to have these in for Alpha 3.