Look for buildhighcpu.tar.gz on support.
I'm on Linux x64, Centos 7.2, beta4.
Apply my user.cfg.xml (included in tarball) and open the workspace.
Before doing the build, make sure you are putting compile output in editor window: "Send compile output to editor window".
Also, before doing the build, run "top" in a different window so you can see the CPU utilization of "vs_exe". Keep the top window visible and put SE in the foreground.
Now start the build. It prints quite a bit of stuff and then pauses at a very long link (simulated here with "sleep"). Observe CPU utilization in the visible top window (but keep SE in foreground) during this pause for the long link. You will see that CPU utilization is high (using up at least 1 core fully). Using SE is also very slow at this time, I suspect the main thread is busy repeating error parsing even though no new information is in the build window.