Last week the ASF svn servers were wonky, and they were accepting connections but then hanging. As a result, any Subversion commands were connecting to the server, and then waiting for a response. While that in and of itself is bad, it's not the fault of Subversion, per se. However, I did notice that my CPU usage during the wait was inordinately high. It appeared that serf was in some kind of busy loop which was simply churning CPU cycles, which is bad. This was using a recent-ish 1.7.x build. While I don't expect users to routinely interact with bustified servers, this CPU usage hints to me that other things may be lurking within serf which are consuming many more resources than needed.