Comment 7 for bug 1000164

I'm fairly sure this is a duplicate, but I can't find the older version of the bug right now. I also remember many people talking about the problem being the default kernel scheduling algorithm. But let's leave the bug attached to Unity for now because it's possible Unity is indirectly accessing the disk when that really should be avoided (for this very reason).