High CPU load with Compiz on Ubuntu 14

Question

I’m using vuex with a tree of data. It's reactive and works well because we have a corresponding tree of components. Since the structure is a tree, it’s common to want to mutate a deeply nested child object. The easy way to implement that is with a mutation that accepts the child in its payload:

removeLeaf(state, { child, leaf }) {
  child.children = child.children.filter((i: any) => i !== leaf);
  state = state; // silence warning
},

A different way would be to change the mutation to work like this:

removeLeaf(state, { child_, leaf }) {
  let child = searchForChild(state, child_);
  child.children = child.children.filter((i: any) => i !== leaf);
},

I’m happy with the first way. Are there any drawbacks to writing mutations that modify a child object of state by using payload instead of the state parameter?

Solution

I had difficulties with this problem on Ubuntu 14.04. The CPU Usage was charged by compiz over 60 %...I followed the instructions from a Bug-report:

1. Download the "Compiz Config Settings Manager" from Ubuntu Apps

2. Run the Compiz Config Settings Manager and select the section OpenGL

3. Turn the option Sync to VBlank off
4. Reboot or log out and in.

After this procedure the CPU Usage of compiz is at 10%..

I hope this helps others as well.

Comments

[ebed]

A working solution is described here - I hope it helps you as much as it helped me!

[Mike Jones]

Ok, I found a solution after a lucky google search. 1) Turn off Parallels 3D 2) Boot 3) Shutdown 4) Turn on Parallels 3D 5) Boot For some reason you need to boot with no 3D followed by 3D. It is slow because 3D acceleration is off, but you need to go through this sequence to make 3D work. An update with 3D enabled broke the driver and this sequence repairs it.

[Admin]

Do you mean to say to turn it off?

[Admin]

Yes, the option "Sync to VBlank" has to be turned off. Greets

[snowguy]

This really helped...but compiz is still taking an unreasonable amount of cpu. Prior to this fix I could hardly do anything it was hogging the CPU so much. Now it is hovering between 80 and 120% on my 4 cpu machine.

[joeforker]

The reactivity appears to be working well. I'll check the logs.

[Kzqai]

Tried this as a Hail Mary and turning off the vaunt almost instantly made the ui more responsive, so thanks for that.