On Tue, Jun 21, 2011 at 09:30, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Stefan Sperling wrote on Tue, Jun 21, 2011 at 15:15:53 +0200: >> On Tue, Jun 21, 2011 at 02:36:11PM +0200, Stefan Sperling wrote: >> > It would be nice to get an official confirmation about this from SF.net. >> > >> > Because if this is the case, I think we should seriously reconsider the >> > decision of making serf the default for 1.7. We definitely cannot afford >> > to break Subversion for all sourceforge users in such a fundamental way. >> > People who can benefit from serf's performance characteristics without >> > facing such problems can still enable it. >> >> For reference, this is the URL I have tested with: >> https://jcl.svn.sourceforge.net/svnroot/jcl/trunk/jcl >> Neon completes the checkout within 2 minutes, but serf is taking >> forever (27 minutes and counting). > > It's also taking 80%-100% CPU and the memory usage grows steadily (a > couple of dozen MB's in this case).
That definitely implies something wrong on the client. If the server is slow, then the client should mostly be blocking. I'll investigate after I finish with this XML parsing thing in ra_serf. (which may fix the observed memory problem) Cheers, -g
