I'm using Fabric 1.0 on Mac OS X 10.6 and am seeing extremely high CPU usage when running sudo() commands. By high CPU usage I mean >90% on all 4 cores on the machine. Is anyone else seeing this and/or know of a fix?
This appears to be caused by having a command that doesn't send any output back for a while - perhaps some sort of busy read polling?
Specifically, I'm seeing this when running chef-solo on a remote machine using sudo(). Some chef commands don't produce output for a while and it's at these points that CPU usage shoots up.