Fabric 1.0 has a new interactivity feature which seems to cause higher
than normal CPU load on some systems. If we get enough feedback from
users we may see about making the interactivity optional or trying to
find an alternate polling method (though that may not be
easy/possible).
-Jeff
2011/3/10 Ivan <b...@mail.ru>:
> My fabfile:
> from fabric.api import run
>
> def test():
> run("sleep 1000")
>
> fab -H localhost
>
> in version 0.9 - all ok, but in 1.0.0 - top show a high cpu usage (100%
> percents). Why ?
>
>
>
> _______________________________________________
> Fab-user mailing list
> Fab-user@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/fab-user
>
>
--
Jeff Forcier
Unix sysadmin; Python/Ruby engineer
http://bitprophet.org
_______________________________________________
Fab-user mailing list
Fab-user@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fab-user
